Skip to content
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

matching: Consider nnkTupleConstr as tuple #86

Merged
merged 1 commit into from
Mar 29, 2021
Merged

Conversation

Clyybber
Copy link
Contributor

A small fix on current devel, and required for nim-lang/Nim#13793

@Araq Araq merged commit fb16554 into nim-lang:master Mar 29, 2021
@timotheecour
Copy link
Member

timotheecour commented Mar 29, 2021

@Clyybber instead, use when defined(nimHasUnifiedTuple) which was introduced in nim-lang/Nim#13793 to maintain stricter checks

@Clyybber
Copy link
Contributor Author

Clyybber commented Mar 29, 2021

@timotheecour
Copy link
Member

ok, will take your word for it :)

haxscramper added a commit to haxscramper/hmisc that referenced this pull request Nov 17, 2021
Considering fusion library has been completely ignored and left to rot in
uncertainty I do not see any reason for me to even *try* to maintain
pattern matching outside of my dependency tree - I don't want to wait of
months before each my fix gets merged only to find that nobody cares enough
to even tag stuff properly (which leads to reports like
nim-lang/fusion#99 **even though the fix has
already been merged** nim-lang/fusion#86 almost a
year ago)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants