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

rusti broken in 0.8, segfaults #9961

Closed
amunra opened this issue Oct 19, 2013 · 1 comment
Closed

rusti broken in 0.8, segfaults #9961

amunra opened this issue Oct 19, 2013 · 1 comment

Comments

@amunra
Copy link

amunra commented Oct 19, 2013

The repl seems rather unstable in 0.8.
$ uname -a
Linux typhoon 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

$ rusti
WARNING: The Rust REPL is experimental and may be
unstable. If you encounter problems, please use the
compiler instead. Type :help for help.
rusti> fn testfunc() { println("testfunc"); }
rusti> testfunc()
Segmentation fault (core dumped)
@thestinger
Copy link
Contributor

It has been removed in master. The 0.8 version was just a tag on master, and doesn't receive any patches.

flip1995 pushed a commit to flip1995/rust that referenced this issue Jan 25, 2024
@GuillaumeGomez
Update trait_duplication_in_bounds.rs ui test to add regression for #…
7217c22 
…rust-lang#9961
flip1995 pushed a commit to flip1995/rust that referenced this issue Jan 25, 2024
@bors
Auto merge of rust-lang#12155 - GuillaumeGomez:fix-9961, r=blyxyas
2067fe4 
Correctly handle type relative in trait_duplication_in_bounds lint

Fixes rust-lang#9961.

The generic bounds were not correctly checked and left out `QPath::TypeRelative`, making different bounds look the same and generating invalid errors (and fix).

r? `@blyxyas`

changelog: [`trait_duplication_in_bounds`]: Correctly handle type relative.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@amunra @thestinger