You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rusti> use core::rand::RngUtil;
()
<anon>:31:0: 31:24 error: `use` and `extern mod` declarations must precede items
<anon>:31 use core::rand::RngUtil;
^~~~~~~~~~~~~~~~~~~~~~~~
error: aborting due to previous error
rust: task failed at 'explicit failure', /Users/danluu/Downloads/rust-0.6/src/libsyntax/diagnostic.rs:99
rusti> assert!(true);
<anon>:31:0: 31:24 error: `use` and `extern mod` declarations must precede items
<anon>:31 use core::rand::RngUtil;
^~~~~~~~~~~~~~~~~~~~~~~~
error: aborting due to previous error
rust: task failed at 'explicit failure', /Users/danluu/Downloads/rust-0.6/src/libsyntax/diagnostic.rs:99
Is this considered to be worth fixing? I think I hack in a kludge that would fix this, but there's this big comment in rusti.c:
/**
* The AST (or the rest of rustc) are not sendable yet,
* so recorded things are printed to strings. A terrible hack that
* needs changes to rustc in order to be outed. This is unfortunately
* going to cause the REPL to regress in parser performance,
* because it has to parse the statements and view_items on each
* input.
*/
If that change will fix it anyway, I'm not sure it's worth making a temporary fix.
The text was updated successfully, but these errors were encountered:
These few commits address a few existing issues:
* #5469 - adding regression tests for `rusti`. This adds unit tests to the `rusti.rc` file (which needed some reorganization of the Makefile, see the first commit message). These are super-simple right now, and sadly can't test the output of the tests. I worked for a bit on making a compiletest version of the rusti tests, but I ended up hitting something which blocked me, although I've forgotten it by this point.
* #5937 - regression test added, and it's fixed
* #5803 - just doesn't appear to happen any more
* #5784 - it's no longer broken, and it no longer spits out warnings about unused variables.
I also did some investigation into #5774, and you may want to read the comment I left on the bug. The gist of the situation is that C++ exceptions across JIT code don't look like they're working, even though they [should be working](https://github.com/mozilla/rust/blob/3aa1122ec25d15a2a73a295f8298ad9c38b09a10/src/rustllvm/RustWrapper.cpp#L387). If anyone has any insight on this, that would be awesome!
option_if_let_else - distinguish pure from impure else expressions
Addresses partially rust-lang#5821.
changelog: improve the lint `option_if_let_else`. Suggest `map_or` or `map_or_else` based on the else expression purity.
Is this considered to be worth fixing? I think I hack in a kludge that would fix this, but there's this big comment in rusti.c:
If that change will fix it anyway, I'm not sure it's worth making a temporary fix.
The text was updated successfully, but these errors were encountered: