-
Notifications
You must be signed in to change notification settings - Fork 5
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
'broadcast use' not handled correctly #86
Comments
I was surprised to see the differing indentations in your output. That seems to be an unrelated copy-paste issue, since I get the following on v0.4.0, so my message below assumes this output: broadcast use
super::raw_ptr::group_raw_ptr_axioms,
super::set_lib::group_set_lib_axioms,
super::set::group_set_axioms,
; Imho, this is something where the Verus parser could be made more permissive with the the trailing comma. While we could update verusfmt to not have the trailing comma, I believe that given Verus's stance on bulleted expressions (such as with the introduction of As a workaround for now (until a decision is made), you can use: broadcast use super::raw_ptr::group_raw_ptr_axioms;
broadcast use super::set_lib::group_set_lib_axioms;
broadcast use super::set::group_set_axioms; which prevents the addition of the |
i have no strong opinions. fixing either on the verus parser end or the verusfmt end would be sufficient |
Honestly, IMO the right thing to do is to require braces around the broadcast use list. This is an oversight of mine in terms of consistency with Rust's |
Sounds good. I've implemented the braced With the braced broadcast use, the above example would output: broadcast use {
super::raw_ptr::group_raw_ptr_axioms,
super::set_lib::group_set_lib_axioms,
super::set::group_set_axioms,
}; How this suggested change impacts vstd: 4acbe48. |
this:
becomes:
which is not accepted by the verus parser
The text was updated successfully, but these errors were encountered: