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
boolean values are not comparable #1585
Comments
krader1961
added a commit
to krader1961/elvish
that referenced
this issue
Jul 25, 2022
krader1961
added a commit
to krader1961/elvish
that referenced
this issue
Jul 25, 2022
krader1961
added a commit
to krader1961/elvish
that referenced
this issue
Jul 25, 2022
krader1961
added a commit
to krader1961/elvish
that referenced
this issue
Jul 25, 2022
xiaq
pushed a commit
that referenced
this issue
Aug 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While working of #1570 I tried this to verify that a constant key results in no change to the order of the inputs:
I thought I had a bug in my
&key
implementation but it turns out that the current Elvish implementation does not support comparing booleans:Yes, this is an odd thing to do but it should be possible to compare booleans. Note that this isn't a problem with the
order
command -- it's a problem with thecompare
command (whose implementationorder
uses for comparisons):The text was updated successfully, but these errors were encountered: