RichardWepner

Hello there, first of all, I'm not an Extenject developer, but just another user myself. Looking at the code, it looks like this exception occurs if there's an assembly that...

Hello there, to be honest, I'm just another developer who used Extenject before, so I can't guarantee to have all the knowledge one could have regarding Extenject, so I might...

I just did a quick search to see how this could be done (I didn't yet do any VSCode Extension development). In [extension.ts line 26](https://github.com/IJustDev/Gitea-VSCode/blob/master/src/extension.ts#L26), an instance of MarkdownIt is...

Hello there, first of all, I'm not a developer of Extenject, so at the moment I can only give some educated guesses about why this is done. While initializing newly...

Hello there, first of all, I'm not a developer of Extenject, but just another user of the library. To me, it sounds (in general) like a reasonable feature to ask...

The file `zenject.asmdef` got renamed to `Zenject.asmdef`, but the corresponding `*.meta` file wasn't renamed to `Zenject.asmdef.meta` accordingly. On Windows, this shouldn't make a noticeable difference, but on any other system...

I stumbled over the problem with `ref` myself (and had to adjust the issue text here). It would be interesting to know what problems you encountered with `in`, though. Are...

@EricBatlleTripledot: just a minor hint, but if you write extension methods for `struct`s, it's typically advantageous to pass them around by reference, either using `ref` or `in`.