followup now that https://github.com/nim-lang/Nim/issues/15511 was fixed #103
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
|
ping @nitely |
|
@genotrance Is it alright with you if we drop support for Nim < 1.0? |
|
Yes seems about time. |
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.
--gc:arccauses: Error: cannot create an implicit openArray copy to be passed to a sink parameter #81I've dropped support for nim < 1.0 otherwise the change i did via toSeq doesn't work, if for some reason that's not desirable I can use a
whento support it. I dont' see much value in supporting nim < 1.0 at this point though (more opportunities for simplifying code).