-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unbundle DrNim #431
Comments
I'm not against it but historically projects of mine that depend on the Nim compiler API bitrot quickly unless they are part of Nim's repository. |
Ok, then it can move forwards (?). 🤔 |
This comment has been minimized.
This comment has been minimized.
Maybe this should be a sign that the Nim compiler API should be a bit better defined/documented. NimLSP seems to work fine (well, it doesn't crash more the further along the version of Nim you go), but I suspect that is only because it wraps Nimsuggest which does all the actual interfacing. Maybe moving some of your tools into their own separate repositories and maintain them there with the compiler changes would benefit other users of the same API. |
Rotten code in your compiler distribution is not a good Marketing for new companies to migrate to Nim. |
As if they would know, but fine, migrate it to nim-lang/drnim or araq/drnim then. |
@Araq I have seen it multiple times, thats the reason I try to remove the Telemetry from choosenim, |
Roadmap for future is here #437 (comment) |
So this RFC has no concrete response since 2021, See also #476 |
It's just a bad idea. The compiler API keeps changing and at the same time ensuring DrNim keeps working is close to zero work. |
"Do not bite off more than you can chew" kinda situation with DrNim,
I think it should be unbundled from the compiler installers, because is not very useful in its current state.
koch
it.https://github.com/nim-lang/Nim/tree/devel/drnim
The text was updated successfully, but these errors were encountered: