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.

Sign up for GitHub

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

Jump to bottom

Dafny strings need a lexicographic comparison operator #1070

Open
davidcok opened this issue Jan 28, 2021 · 2 comments
Open

Dafny strings need a lexicographic comparison operator #1070

davidcok opened this issue Jan 28, 2021 · 2 comments
Labels
kind: enhancement Enhancements, feature requests, etc. These are NOT bugs, but ways we can improve Dafny priority: not yet Will reconsider working on this when we're looking for work

Comments

@davidcok
Copy link
Collaborator

The < and <= operators on strings mean prefix operations (unfortunately, IMHO).
Dafny should have an intuitive, compact syntax for lexicographic comparison as well (or instead).
@robin-aws
Copy link
Member

Even better, is it worth considering a mechanism for user code to define those operators for a given type?

@RustanLeino RustanLeino added this to the Dafny 3.1 milestone Feb 3, 2021
@RustanLeino RustanLeino added the kind: enhancement Enhancements, feature requests, etc. These are NOT bugs, but ways we can improve Dafny label Feb 3, 2021
@robin-aws
Copy link
Member

Explicitly linking this to #413, as addressing that might mean making a string something other than an alias for a seq of something, which would simply solving this problem.

@atomb atomb removed this from the Dafny 3.1 milestone Apr 21, 2022
@MikaelMayer MikaelMayer added the priority: not yet Will reconsider working on this when we're looking for work label Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind: enhancement Enhancements, feature requests, etc. These are NOT bugs, but ways we can improve Dafny priority: not yet Will reconsider working on this when we're looking for work
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@atomb @MikaelMayer @davidcok @RustanLeino @robin-aws