-
Notifications
You must be signed in to change notification settings - Fork 38
Nim extension in Nim #172
Comments
Just a quick update, I believe I'm about 1/3rd of the way through conversion. That's feelings more than math, I'll check later how many files/features/functions/whatever I have left to convert. But almost through all the nimSuggest items. |
Finished porring all the providers etc... Now it's into a whole lot of the backend like the indexer. I also need to learn more Nim because I'm still writing typescript/haxe with a different syntax. Going through this part, looking at nimSuggest integration etc, I think one of the things to do after a bit of house keeping is working to integrate the language server protocol. It should help consolidate efforts and help move the focus of the extension on user experience, UI, and services, while keeping much of the heavy lifting and enabling work in a shared place to help everyone. |
Quick update, down to one last file, nimMain.ts. Highlights:
My current "minimal" todo list:
|
OK, all the typescript code has been ported over. 🎉 Next up:
The first point is because I'm presuming folks in this project don't want to rush towards it just yet. |
Switched to your version @saem I'll report any issue I find. Cheers! |
Thanks, @kraptor. My version is probably pre-alpha, at best. I just published a test version to learn. Nonetheless, I'm grateful for the support and I'll keep an eye out. |
Finished porting https://marketplace.visualstudio.com/items?itemName=nimsaem.nimvscode. I created a new repo that's no longer a fork of this one, so it has its own issue tracker. Now comes the fun of refactoring and maybe some other contributors. Closing this issue for now. |
Wasn't quite sure where else to put it, I'm seeing if I can port the TypeScript code this extension is written in into Nim -- you can follow that branch here.
It's a fun way for me to learn a bit of Nim (read: the code is ugly and a straight port). If I complete it, well that might make community contributions a whole lot easier and allow for leveraging a lot more pure Nim facilities. My intentions are:
If there is interesting in discussing integration just wondering how, if at all, that might proceed?
The text was updated successfully, but these errors were encountered: