8 ms·
Announcing Rust 1.16
- shock 10y agoI'm eagerly awaiting a release of RLS that is installable via rustup.
- eptcyka 10y agoIt will probably end up being installed by `cargo install` anyway. What I can't wait for is Tokio for Diesel and Rocket.
- steveklabnik 10y agoThe plan is for it to be a component in rustup, rather than through cargo install. It needs to be extremely tied to the exact rust version you're on.
- btkramer9 10y agoHave you found any good tutorials for Rocket? The one on Rocket's website is detailed but doesn't go beyond an extremely basic website.
- kybishop 10y agoThe examples in the repo[1] are fairly extensive, and you can always ask questions in the IRC channel[2]. I've found #rocket to be extremely gracious with their time. [1] https://github.com/SergioBenitez/Rocket/tree/master/examples https://github.com/SergioBenitez/Rocket/tree/master/examples [2] https://riot.im/app/#/room/#mozilla_#rocket:matrix.org https://riot.im/app/#/room/#mozilla_#rocket:matrix.org
- 0xFFC 10y agoMe too exactly
- nrc 10y agoWe're literally hacking on this right now. It should be part of the early June stable release.
- FlyingSnake 10y agoI might be a minority here, but can someone please update me on there state of Rust on iOS? I develop C++ cross platform iOS/Android apps and would love to use Rust if possible. The last time I checked Rust didn't support .frameworks creation, didn't support Bitcode and calling the main thread from Rust wasn't easy. I would love to hear if these issues have been resolved.
- agmcleod 10y agoI haven't seen much on it. Doesn't mean solutions don't exist, but I regularly read updates on reddit and what people are working on, and I haven't seen much there. I feel like Swift is more likely to fill that role by coming to android.
- pjmlp 10y agoI imagine just like with Objective-C, it will only happen with forks of the NDK, as Google has always removed it from clang builds.
- steveklabnik 10y agoI hadn't heard of the .frameworks or "calling the main thread" problems; do you know if there are issues open? Bitcode is tough, see https://github.com/rust-lang/rust/issues/35968 https://github.com/rust-lang/rust/issues/35968 In general, we'd love to get this into better shape, but need some help from people with the time and expertise to hack on it.
- FlyingSnake 10y agoHey no worries, you guys are doing great! To be fair to Rust, it does perfectly what it's supposed to do as a language on iOS/Android. I have a fully multithreaded toy Rust+Swift app that works fine, and the performance is pretty good. Most of the problems I described are due to the differences in the paradigms between Swift/Java and Rust. (OOP vs Functional), and I'm sure things will be fine with time.
- pjmlp 10y ago
- AsyncAwait 10y agoProbably the most significant addition in this release is the cargo check subcommand, which does all the type/safety checking part of rustc, but skips the LLVM part of generating the actual binary. If you just want to make sure you code compiles, this is the command for you. There's also a bunch of API stablilizations around Strings, Vectors etc, complete changelog: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1160-2017-03-16 https://github.com/rust-lang/rust/blob/master/RELEASES.md#ve... Congratulations to everyone involved on the release!
- tupshin 10y agoYes, this is huge. It dramatically reduces the code/does-it-compile cycle, which is far more important than the code/run cycle, for rust development.
- hawkice 10y agoI like rust a lot, but even hello world web apps compile (and recompile) so slowly. I barely get a single step down my to do list before recompiles take more than a second, and it makes it functionally unusable compared to other tools. I know this sounds silly, but it's true. I don't want the check, I want to see the webpage changed after my code changes. I keep hearing about incremental compiles but when I used nightly and tried turning it on, I guess it didn't work because compile times barely changed.
- steveklabnik 10y agoIncremental recompilation is still underway; expect some news on it reasonably soon. Even then, it's just the start, and there's more that we can do.
- wst_ 10y agoWhen it's out, can we actually get the same responsiveness as, let's say Java? I assume it also depends on the IDE but I would really like to see instant hints during coding session, ex. when I make mistakes.
- steveklabnik 10y agoI'm not sure what the lower bound is, to be honest. It's not a thing I personally work on.
- karan85 10y agoYou can already get instant hints now with VS Code and the Rust Language Server (RLS). It's still in alpha and the initial setup is a bit involved, but it already works very well for me. https://github.com/rust-lang-nursery/rls https://github.com/rust-lang-nursery/rls https://github.com/jonathandturner/rls_vscode https://github.com/jonathandturner/rls_vscode For some reason, code completion via Racer doesn't work yet for me via RLS, so I use the "old" RustyCode extension for that (https://github.com/saviorisdead/RustyCode https://github.com/saviorisdead/RustyCode).
- sametmax 10y ago1.16 already! Do they sleep ?
- steveklabnik 10y agoWe used a time-based release schedule; each minor version comes out every six weeks. We believe this approach is better for a number of reasons, including quality.
- sametmax 10y agoBut this is a thing that amazes me: the rust community manage to be incredibly productive while maintaining a culture of rigorous quality. In a world of "move fast and break things" at best and just of "I don't know what I'm doing" at worst I find it fascinating to witness.
- dbaupp 10y agoThe theory is that the "not rocket science" rule is a major reason why this is possible: http://graydon2.dreamwidth.org/1597.html http://graydon2.dreamwidth.org/1597.html .
- brson 10y agoHonestly, it's extremely taxing to maintain this pace without everything falling apart. The size of the team employed by Mozilla is quite modest. Firefox, which has a similar release schedule, has an entire team dedicated to just getting the releases out (though Firefox is yet the significantly larger product). We have no entire people, but employ some very rigorous testing.
- hueving 10y ago>We have no entire people You mean people dedicated to releases, or just that everyone must cut off an appendage to join the team? :)
- 10y ago
- ComputerGuru 10y agoThis releases fixes the #derived mess, right? Meaning we don't need to mess with weird build scripts to get serialization and json support? Edit: so it was 1.15! I've been running 1.14 on my laptop and didn't realize it!
- kosinus 10y agoThat was 1.15, I believe. :-)
- deleted 10y ago[deleted]
- steveklabnik 10y agoThat came out in the last release, 1.15: https://blog.rust-lang.org/2017/02/02/Rust-1.15.html https://blog.rust-lang.org/2017/02/02/Rust-1.15.html
- EugeneOZ 10y agoThank you SO MUCH for 'cargo check'! 5-times faster for our biggest project.
- EugeneOZ 10y agoAlthough you broke your promise about avoiding breaking changes. I know I know, it wasn't promise and wasn't about breaking changes, it was something else about something else. "The attribute `export_macro` is currently unknown to the compiler" - what a surprise in beta 1.17.
- steveklabnik 10y agoIt's macro_export, not export_macro https://github.com/rust-lang/rust/issues/40487 https://github.com/rust-lang/rust/issues/40487 That said, regressions happen, which is why beta exists. If you find them, please file them!
- EugeneOZ 10y agoIt's not in my lib and issue is filled. That said, thanks :)
- zellyn 10y ago-Z time-passes Well played, Rust devs, well played. https://imgur.com/a/lK1BQ https://imgur.com/a/lK1BQ
- steveklabnik 10y agoHa! I am pretty sure this is serendipity; -Z is our catch-all "unstable/internal flags" marker.
- riquito 10y agoSince Rust people read hn... the version 1.16 is at the bottom of https://thanks.rust-lang.org/ https://thanks.rust-lang.org/, while it should appear before 1.15
- steveklabnik 10y agoThere's a bug open about this, and I am literally deploying the fix right now. It'll probably be fixed by the time you read this comment :) (EDIT: deployed successfully, refresh the page) Thank you!
- riquito 10y agoHi Steve, thank you. Can you link the bug so that I know where to look at the next time?
- steveklabnik 10y agohttps://github.com/rust-lang-nursery/thanks/issues/61 https://github.com/rust-lang-nursery/thanks/issues/61
- eriknstr 10y agoI am glad that FreeBSD is on the "Tier 2" list of supported platforms [1] but am wondering, is there any way to convince you guys to make it "Tier 1"? If so, how? I am willing to dedicate some amount of my own time to make it happen but am not convinced that my skills [2] and the amount of time I have available to spend is sufficient to make a difference. [1]: https://forge.rust-lang.org/platform-support.html https://forge.rust-lang.org/platform-support.html [2]: https://www.github.com/eriknstr https://www.github.com/eriknstr
- steveklabnik 10y agoSemi-official answer since this isn't an area I work on directly: In general, the differences between Tier 2 and Tier 1 are: 1. Get tests running on every commit. 2. Gate building on those tests passing. The first is a technical/money issue, the latter is a social issue. That is, getting all tests working is technical, being able to afford running them on every commit is monetary, but gating builds on failures on a platform is an issue of "who is responsible for making sure things stay passing." Given that we run these tests on every commit, in some sense, it would be the PR author's job, but if they get stuck, we need someone who's able to help them fix that. That is the hardest part of moving from tier 2 to tier 1 in my personal opinion. Who is that person? What happens if they drop off the project?
- eriknstr 10y ago>Given that we run these tests on every commit, in some sense, it would be the PR author's job, but if they get stuck, we need someone who's able to help them fix that. That is the hardest part of moving from tier 2 to tier 1 in my personal opinion. Who is that person? What happens if they drop off the project? I would have liked to volunteer as the kind of person that would investigate issues for the FreeBSD platform but as I said, both my skills and my time are limited to the extent that they might not be sufficient. As for what happens if the person responsible for this drops off the project, I think the solution to that is not so complicated; demote the platform back to tier 2 until someone else (if anyone ever) steps up to take over the responsibility.
- Animats 10y agoIf you have a previous version of Rust installed, getting Rust 1.16 is as easy as: $ rustup update stable Nah. The old "rustup.sh" script doesn't install "rustup", the application. Rust isn't in the Ubuntu distribution, either. Stop rolling your own installer and use the distro programs. You are not a special snowflake.
- steveklabnik 10y ago> Nah. The old "rustup.sh" script doesn't install "rustup", the application. rustup.sh has been deprecated for months now. > Rust isn't in the Ubuntu distribution, either. It's in Debian now, so (as far as I know) that means it should end up in Ubuntu soonish. > Stop rolling your own installer and use the distro programs. Not everyone is on Linux.
- glandium 10y agoFWIW, Debian unstable is stuck on rustc 1.14.0. You need experimental to, at the moment, get 1.15.1 (no 1.16 yet, but it's a tad early for that ; but in multiple occasions it took weeks to get new rustc releases into Debian). Cargo in Debian, on the other hand, is stuck on 0.15.0... (current version for "stable rust" is 0.17.0) ; no newer version in experimental...
- steveklabnik 10y agoYeah, Stretch just missed 1.15, it's a shame IMHO. They're fine with it though. Now that we've gotten a lot of the kinks worked out, hopefully it won't be weeks in the future.
- Ar-Curunir 10y agoNo need to be hostile.
- runeks 10y agoPersonally I love this feature in a build tool. The Stack tool for Haskell does the same, which means I can use the newest version very easily, without depending on some volunteer's Ubuntu PPA (which may not exist).
- amelius 10y agoI'm wondering if the following will be one day possible with Rust. I want to build a fast data-store with the basic data-structures offered by Rust (e.g., std::collections), which are stored in a memory-mapped file. The problem with mmapped files is that they don't always appear at the same address (this is not always possible, especially if you open multiple stores at once). So in order to use the standard data-structures, Rust must provide some mechanism to make this possible (I realize that this can be tricky). Alternatively, I could write my own data-structures, but of course, I'd prefer to use the standard ones.
- fnord123 10y ago>I want to build a fast data-store Usually this means you want to build things build on arrays. >The problem with mmapped files is that they don't always appear at the same address i.e. you use arrays and then index into the array instead of using pointers. > So in order to use the standard data-structures, Rust must provide some mechanism to make this possible Well, arrays exist in Rust. Or you're going to have to be more specific about what you're trying to do.
- amelius 10y ago> Or you're going to have to be more specific about what you're trying to do. I want to allocate arrays, maps, etcetera inside the region of a memory mapped file. Then, later, when I mmap the same file to a different region in memory, I want the arrays and maps to still work. That's all.
- steveklabnik 10y agoThere are several mmap crates, but they won't let you transparently use std::collections on top of them. I imagine this will be possible once the custom allocators work sorts out.
- dbaupp 10y agoJust having custom allocators won't automatically fix the pointer issue: remapping the file later will leave the previously "allocated" pointers pointing into old memory, which may not be where the file was remapped. The allocators and data structures would need to support using non-raw-pointer pointers types, including not even platform-pointer sized types.
- tedunangst 10y agoThe speed up for diesel appears mistyped.
- steveklabnik 10y agoGah, I can't do basic math it seems. I'll fix it tomorrow.