testing nim features #17
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm just exploring some Nim features to reason about how could we simplify the developer experience:
Using, because we need add
propsandeventeverywhere.html(fmt"<i/>")->fmt"<i/>", at least in your exemple code it looks reasonableexportc-> 'jso', JSO isn't a good name, but exportc is worse, unseless we are working with C code. I woul'd prefer some from standard in nim lib.component,eventandappas template, it almost nullifies the reasons for 1 .I would prefer
importinstead ofinclude, but it doesn't work with 3, and I'm not sure about 1.Anyway, is more like a forum post than a "PR", but is more readable as "PR" than an issue, please close after reading. ;-)