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

Typechecking doesn't enforce communication immutability requirements #568

Closed
eholk opened this issue Jun 24, 2011 · 4 comments
Closed

Typechecking doesn't enforce communication immutability requirements #568

eholk opened this issue Jun 24, 2011 · 4 comments
Assignees
@brson
Labels
A-typesystem Area: The type system
Milestone
0.1 first support...

Comments

@eholk
Copy link
Contributor

eholk commented Jun 24, 2011

It looks like we'll still attempt to compile attempts to send mutable data on channels or in spawn arguments. This should be disallowed.
@ghost ghost assigned eholk Jun 24, 2011
@eholk
Copy link
Contributor Author

eholk commented Jun 27, 2011

It looks like this depends on having the kind system in place (#234 and #132).

@ghost ghost assigned eholk Jun 27, 2011
@brson
Copy link
Contributor

brson commented Sep 28, 2011

The only thing left to do here is immutable closures (fn~) or bare functions

@ghost ghost assigned brson Oct 6, 2011
@brson
Copy link
Contributor

brson commented Oct 10, 2011

Depends on #1022

@brson
Copy link
Contributor

brson commented Oct 21, 2011

Done.

@brson brson closed this as completed Oct 21, 2011
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
@bors
Auto merge of rust-lang#568 - anatol:add_MINSIGSTKSZ, r=alexcrichton
26b8ab3 
Add MINSIGSTKSZ constant to linux sources

MINSIGSTKSZ is a minimum size of process stack allowed
flip1995 pushed a commit to flip1995/rust that referenced this issue Nov 5, 2020
@hegza
Implement field_reassign_with_default
7b203f3 
- Implement `field_reassign_with_default` as a `LateLintPass`
- Avoid triggering `default_trait_access` on a span already linted by
`field_reassigned_with_default`
- Merge `default_trait_access` and `field_reassign_with_default` into
`Default`
- Co-authored-by: Eduardo Broto <ebroto@tutanota.com>
- Fixes rust-lang#568
flip1995 pushed a commit to flip1995/rust that referenced this issue Nov 5, 2020
@bors
Auto merge of rust-lang#5911 - hegza:issue-568, r=ebroto
5b52474 
Add lint for 'field_reassign_with_default` rust-lang#568

changelog: Add lint for field_reassign_with_default that checks if mutable object + field modification is used to edit a binding initialized with Default::default() instead of struct constructor.

Fixes rust-lang#568

Notes:
- Checks for reassignment of one or more fields of a binding initialized with Default::default().
- Implemented using EarlyLintPass, might be future proofed better with LateLintPass.
- Does not trigger if Default::default() is used via another type implementing Default.
- This is a re-open of [PR#4761](rust-lang/rust-clippy#4761), but I couldn't figure out how to re-open that one so here's a new one with the requested changes :S
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
@wsmoses
Handle hypot (rust-lang#568)
5c89a86
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brson brson

Labels
A-typesystem Area: The type system
Projects
None yet
Milestone
0.1 first supported public release
Development

No branches or pull requests
2 participants
@eholk @brson