Skip to content

Mutable keyword on reference arguments is redundant #964

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Closed
brson opened this issue Sep 23, 2011 · 1 comment
Closed

Mutable keyword on reference arguments is redundant #964

brson opened this issue Sep 23, 2011 · 1 comment

Comments

@brson
Copy link
Contributor

brson commented Sep 23, 2011

These two are the same now I believe

fn f<@T>(&o: mutable option::t<T>) {
    assert o == option::none;
}

fn f<@T>(&o: option::t<T>) {
    assert o == option::none;
}
@brson
Copy link
Contributor Author

brson commented Sep 23, 2011

Oh, that 'mutable' triggers the 'ignoring deprecated mutable type constructor' warning. Think I will close this issue and open another one to remove deprecated mutable type constructors.

@brson brson closed this as completed Sep 23, 2011
@venkag venkag mentioned this issue Feb 13, 2019
Closed
ZuseZ4 added a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
@ZuseZ4
Move rust bindings into rustc (rust-lang#964)
fe550b5
coastalwhite pushed a commit to coastalwhite/rust that referenced this issue Aug 5, 2023
@DevJPM
Add AVX512BITALG (rust-lang#964)
8f09ef7 
This adds the AVX512BITALG intrinsics.
It also patches the verification against the Intel Intrinsic Guide
because Rust uses a different naming.
Added intrinsics match _mm(256|512)?(_maskz?)?_popcnt_epi(8|16) for the popcount ones
and _mm(256|512)?(_mask)?_bitshuffle_epi64_mask
celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@celinval @tedinski
Hide --lib-c and add assume-false to unknown fns (rust-lang#964)
4166069 
 - Support to --lib-c is not well tested. Keep it as experiemental.
 - Change how CBMC behaves when a function that is not defined is
   reachable. This mitigates issues rust-lang#576. We should still add an
   unimplemented assertion so we can flip the results of other checks to
   undetermined.
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brson