Shawn Carere

Hi @rodolphebarbanneau, thankyou for responding. I see what you're saying. I was going to suggest assuming all return parameters are types and all argument parameters are names if only a...

I should note that I don't think I've fixed a memory leak so much as I have addressed an issue with memory not being cleaned up enough frequently causing OOM's....

Also the nnunet client would randomly just not work sometimes. It might have been OOM issues, but it also might have been something to do with torch.compile. The nnunet model...

> Pretty much good to go! I just want to get your take on the one comment I left before getting this merged in. > > I also tried to...

Also forgot to mention that return types that start with a capital letter (eg. Callable, Sequence) are mistaken as sections. Further more if the type has square brackets (eg. Sequence[str])...

Just noticed another case in which highlighting doesn't work. In numpy docstrings one can have two parameters of the same type on the same line. Eg. ```python """ Parameters ---------------...

@rodolphebarbanneau thank you for your additional comments. I will definitely rate the extension on the marketplace to support it as I do find this to be a useful extension. I...

I'd also like to mention that a nice long-term goal to add as a feature would be seperate themes/custom themes without having to manually edit the settings.json. perhaps a path...

Attribute interface would be better as it would be consistent with the rest of the api. Ei ```python fndocs = parse(fn.__doc__) fndocs.params.argument1.description ``` Is cleaner than: ```python fndocs = parse(fn.__doc__)...

I'm not sure what you mean. Right now the Docstring class has attribute params with type List[DocstringParam]. Instead we could have ```python class DocstringParams(): def __init__(self, params_list: List[DocstringParam]): for param...