Language Selection

English French German Italian Portuguese Spanish

Rust 1.39.0 Release and Beyond

Filed under
Development
  • Announcing Rust 1.39.0

    The Rust team is happy to announce a new version of Rust, 1.39.0. Rust is a programming language that is empowering everyone to build reliable and efficient software.

    [...]

    The highlights of Rust 1.39.0 include async/.await, shared references to by-move bindings in match guards, and attributes on function parameters. Also, see the detailed release notes for additional information.

  • Rust 1.39.0 released

    Version 1.39.0 of the Rust language is available. The biggest new feature appears to be the async/await mechanism, which is described in this blog post: "So, what is async await? Async-await is a way to write functions that can 'pause', return control to the runtime, and then pick up from where they left off. Typically those pauses are to wait for I/O, but there can be any number of uses."

  • Async-await on stable Rust!

    On this coming Thursday, November 7, async-await syntax hits stable Rust, as part of the 1.39.0 release. This work has been a long time in development -- the key ideas for zero-cost futures, for example, were first proposed by Aaron Turon and Alex Crichton in 2016! -- and we are very proud of the end result. We believe that Async I/O is going to be an increasingly important part of Rust's story.

    While this first release of "async-await" is a momentous event, it's also only the beginning. The current support for async-await marks a kind of "Minimum Viable Product" (MVP). We expect to be polishing, improving, and extending it for some time.

    Already, in the time since async-await hit beta, we've made a lot of great progress, including making some key diagnostic improvements that help to make async-await errors far more approachable. To get involved in that work, check out the Async Foundations Working Group; if nothing else, you can help us by filing bugs about polish issues or by nominating those bugs that are bothering you the most, to help direct our efforts.

  • Support lifecycle for Clang/LLVM, Go, and Rust in Red Hat Enterprise Linux 8

    The Go and Rust languages continue to evolve and add new features with each compiler update, which is why so many users are interested in getting the latest versions of the compilers. At the same time, these compilers are designed to remain compatible with older code. So, even as we advance to newer versions of Go and Rust within the RHEL 8 application streams, you should not need to update your codebase to keep it compilable. Once you’ve compiled your valid code using the Go or Rust application stream, you can make the assumption that it will continue to compile with that stream for the full life of RHEL 8.

    We are excited to continue to bring you the latest and greatest in new compiler technologies. Stay tuned to the Red Hat Developer blog to learn more about what you can do with LLVM, Go, and Rust.

Rust 1.39 Released With Async-Await Support

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Security: Windows Ransomware and Malware, New Patches and More

  • Ransomware attacks on business, government pick up pace

    Ransomware attacks on businesses and governments will continue at a more rapid pace, thanks to newly found security vulnerabilities, according to one global security firm which forecasts further increases in ransomware attacks and VPN “scandals” in 2020 and beyond.

  • ThreatList: A Third of Biometric Systems Targeted by Malware in Q3 [iophk: Windows TCO]

    Kaspersky researchers found that in the third quarter, one in three (37 percent) of computers within the firm’s telemetry that collect, process and store biometric data were targeted by malware attacks. The malware in question included spyware and remote access trojans (RATs), which accounted for 5.4 percent of all computers analyzed; followed by malware used in phishing attacks (5.1 percent), ransomware (1.9 percent) and trojan bankers (1.5 percent).

  • Biometric data processing and storage system threats

    Thirdly (and most importantly), biometric data, once compromised, is compromised for good: users cannot change their stolen fingerprints the way they do stolen passwords. What’s more, biometric data may turn out to be compromised for all applications at the same time. An individual will therefore potentially be affected for the rest of his or her life.

    Given all of the issues above, it is remarkable how careless biometric authentication system developers and users are about protecting these systems and the biometric data collected by them against computer attacks.

  • Security updates for Thursday

    Security updates have been issued by Arch Linux (firefox), Fedora (cyrus-imapd, freeipa, haproxy, ImageMagick, python-pillow, rubygem-rmagick, sqlite, squid, and tnef), openSUSE (haproxy), Oracle (microcode_ctl), and Ubuntu (squid, squid3).

  • Aviatrix VPN vulnerability left user endpoints wide open

    Aviatrix, a supplier of open source enterprise virtual private networks (VPNs) to customers including BT, Nasa and Shell, has patched a serious vulnerability in its client that could have given an attacker escalation privileges on a machine to which they already had access. The vulnerability was uncovered by Immersive Labs researcher and content engineer Alex Seymour, after noticing that the VPN client was unusually verbose when booting on a Linux machine. Its disclosure comes hot on the heels of government warnings about the possibility of state-sponsored threat actors targeting high-profile organisations through VPN vulnerabilities in products from the likes of Pulse Secure, Palo Alto Networks and Fortinet.

FSF and FSFE: Showcase and Community Meeting in Bolzano, Italy

  • The FSF tech team: doing more for free software

    At the Free Software Foundation (FSF), we like to set big goals for ourselves, keeping a relatively small group of dedicated activists determined to cover a lot of ground in a short time.The FSF tech team, for example, has just four members -- two senior systems administrators, one Web developer, and a part-time chief technology officer -- yet we manage to run over 120 virtual servers. These run on about a dozen machines hosted at four different data centers. These include many public-facing Web sites and community services, as well as every single IT requirement for the staff: workstations, data storage and backup, networking, printing, accounting, telephony, email, you name it. We don't outsource any of our daily software needs because we need to be sure that they are done using only free software. Remember, there is no "cloud," just other people's computers. For example: we don't outsource our email, so every day we send over half a million messages to thousands of free software hackers through the community mailing lists we host. We also don't outsource our Web storage or networking, so we serve tens of thousands of free software downloads -- over 1.5 terabytes of data -- a day. And our popularity, and the critical nature of the resources we make available, make us a target for denial of service attacks (one is ongoing as we write this), requiring constant monitoring by the tech team, whose members take turns being ready for emergency work so that the resources our supporters depend on stay available. As hard as we work, we still want to do more, like increasing our already strict standards on hardware compliance, so in 2020, we will finish replacing the few remaining servers that require a non-free BIOS. To be compliant to our own high standards, we need to be working with devices that are available through Respects Your Freedom retailers. We plan to add new machines to our farm, so that we can host more community servers like the ones we already host for KDE, SugarLabs, GNU Guix, Replicant, gNewSense, GNU Linux-Libre, and FSFLA. We provide completely virtual machines that these projects use for their daily operations, whether that's Web hosting, mailing lists, software repositories, or compiling and testing software packages. We know that many software projects and individual hackers are looking for more options on code hosting services that focus on freedom and privacy, so we are working to set up a public site that anybody can use to publish, collaborate, or document their progress on free software projects. We will follow strict criteria to ensure that this code repository hosts only fully free software, and that it follows the very best practices towards freedom and privacy.

  • Report from the 2019 FSFE Community Meeting in Bolzano, Italy

    Report from the 2019 FSFE Community Meeting in Bolzano, Italy This year's FSFE Community Meeting took place from Friday 15 November to Saturday 16 November 2019 as part of SFSCon - an annual Free Software event in the city of Bolzano in South Tyrol, Italy. As in previous editions, embedding our community meeting in another event gave us the opportunity to meet different parts of our own community as well as to connect with people from other communities. On Friday, SFScon started officially and the NOI Techpark transformed into the interim capital of Free Software with talks and booths. Of course, the FSFE booth was also part of it and the booth team commandeered the whole area by installing a balloon chain and putting up posters. The rumours that the booth team gave away free pizza (not as in freedom) to gain more attention, are highly exaggerated, though.

SUSE/OpenSUSE: SUSE Doc Day at SUSECON 2020, OpenSUSE Board Election and More

  • Yes We Do it Again: SUSE Doc Day at SUSECON 2020

    A Doc Day is a time when a group of people gathers to collaborate on writing documentation on one or more given topics. The main premise for our Doc Day is to get a group of interested people – YOU – in a room together and have you work towards shared goals. To help you feel more comfortable, we will give a short overview of our documentation, how we usually work, and how you can contribute. Of course, you cannot write entire manuals or guides in one single day. But you can help us to improve existing documentation by reviewing, editing and updating it. In addition, we will use the Doc Day to kick-off the creation of new guides and papers for topics that you think are not yet covered (well enough).

  • openSUSE Board election 2019-2020 – Call for Nominations, Applications

    Two seats are open for election on the openSUSE Board. Gertjan Lettink completed his second term. Simon Lees completed his first term and thus he is eligible to run as a Board candidate again should he wish to do so.

  • status.opensuse.org updated

    Our infrastructure status page at https://status.opensue.org/ is using Cachet under the hood. While the latest update brought a couple of bugfixes it also deprecated the RSS and Atom feeds, that could be used to integrate the information easily in other applications. While we are somehow sad to see such a feature go, we also have to admit that the decision of the developers is not really bad - as the generation of those feeds had some problems (bugs) in the old Cachet versions. Instead of fixing them, the developers decided to move on and focus on other areas. So it's understandable that they cut off something, which is not in their focus, to save resources.

  • SSL cipher updates

    Sometimes it's a good idea to follow best practices. This is what we did by following the recommendations for "general-purpose servers with a variety of clients, recommended for almost all systems" from https://ssl-config.mozilla.org/.

qBittorrent 4.2.0 Adds Support For Libtorrent 1.2, New Features

qBittorrent 4.2.0 was released recently featuring support for libtorrent 1.2, some minor new features, as well as WebUI updates. qBittorrent is a free and open source BitTorrent client for Windows, macOS, OS/2, Linux and FreeBSD, written in C++ (Qt) and Python (for its optional search engine). It comes with a Qt GUI, but it can also be used on a headless server, without requiring the X window system -- in both GUI and headless mode you can remote control it through its web user interface. The application comes with pretty much everything you'd need in a BitTorrent client, from sequential downloading and bandwidth scheduling to a torrent creation tool, anonymous mode, integrated search engine, RSS feed reader and downloader with advanced filters, IP filtering, and of course support for DHT, PeX, encrypted connections, LSD, UPnP and NAT-PMP port forwarding support, µTP, magnet links, private torrents and more. Read more