Skip to content

deprecate 'obj' in docs #1483

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
Closed
graydon opened this issue Jan 10, 2012 · 2 comments
Closed

deprecate 'obj' in docs #1483

graydon opened this issue Jan 10, 2012 · 2 comments
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Milestone
0.1 first support...

Comments

@graydon
Copy link
Contributor

graydon commented Jan 10, 2012

The obj system will be removed in a near-future version of rust, as we have a typeclass system now that goes a fair ways beyond what the obj system did.

Not first release, but soon. In our own code we're leaving it active for the 0.1 release just to avoid totally destabilizing things. In the meantime we need to remove most discussion of 'obj' from the docs, and mark it as deprecated.

(Sniff. I liked it!)
@ghost ghost assigned graydon Jan 10, 2012
@lkuper
Copy link
Contributor

lkuper commented Jan 11, 2012

Don't shed too many tears. The typeclass system is nice! :)

@graydon
Copy link
Contributor Author

graydon commented Jan 17, 2012

I've removed this from the .md file

@graydon graydon closed this as completed Jan 17, 2012
@graydon graydon removed their assignment Jun 16, 2014
flip1995 pushed a commit to flip1995/rust that referenced this issue Jan 15, 2021
@bors
Auto merge of rust-lang#6538 - Jarcho:vec_init_then_push, r=llogiq
976850b 
New lint: vec_init_then_push

fixes: rust-lang#1483

This will trigger on `new`, `default`, and `with_capacity` when the given capacity is less than or equal to the number of push calls. Is there anything else this should trigger on?

changelog: Added lint: `vec_init_then_push`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
0.1 first supported public release
Development

No branches or pull requests
2 participants
@graydon @lkuper