Skip to main content

Search

Items tagged with: rustlang


#fishshell rewrite-it-in #rust progress, 2023-11-20

76909 rust lines added
48105 / 77063 C++ lines removed
▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░ 62 %

#riir #rustlang

--

So, that's a significant jump - mostly thanks to the merge of the parser rewrite branch, described as "Herculean". The parser, autoloading module, completion module, function management, history management, and the builtins for complete, disown, eval, fg, history, jobs, read, set, and source have all been ported, as well as many other parts of the code.

This also allowed the removal of lots of supporting tools, including the UTF-8 modules, and quite a few bits of the FFI.

After a few months of slow progress this is a huge step forwards.


Built a binary with #RustLang using the `cargo auditable build` command. Running `cargo audit bin <binary>` gives me "parse error: Failed to deserialize audit data from JSON: The input JSON specifies a cyclic dependency graph". Question one: does a cyclic dependency graph in the JSON even matter when auditing the binary? Question two: how do I identify the crates participating in the cycle when tracking it down by hand from the extracted JSON is a rabbit hole due to the vast amount of crates?


Dear #Rust #rustlang devs:

bumping your MSRV is a semver-major bump. It is, in fact, a dick move to your dependents to do an MSRV bump in a semver-patch bump.

Yes, having to do a semver-major bump sucks.

It sucks even worse for your dependents who now have to semver-major with no functionality changes at all, just because of you.

/rant


https://wayofthecrab.com/ #RustLang


Published the new 0.2.0 version of the rustc-tools crate. This tool aims to make rustc internals accessible (as much as possible).

Want to write a few lints for your project without adding them to clippy? Take a look at the example: https://github.com/GuillaumeGomez/rustc-tools/blob/master/examples/lint.rs
Just want a Rust parser? You can too: https://github.com/GuillaumeGomez/rustc-tools/blob/master/examples/ast.rs

Enjoy!

https://crates.io/crates/rustc-tools

#rust #rustlang


Wir suchen #Rust #Entwickler. Anfangs als #teilzeit aber sehr sehr wahrscheinlich wird das zu #Vollzeit wachsen (oder mehrere Teilzeit, wenn das besser passt).

Ort: Voll #Remote - wir haben kein Büro mehr - aber aus vertraglichen und rechtlichen Gründen muss der Arbeitsort innerhalb von .de liegen.
Selten (derzeit einmal im Jahr) eine Fahrt in die Gegend um Frankfurt/Main einzuplanen, Firmenevent.

Nötig: Gute #Rustlang Kenntnisse. Und man sollte andere Sprachen (viel C, etwas Java, Bash) zumindest grob lesen können.
Es geht ums (Neu/Um)schreiben von Applikationen.
Außerdem Umgang mit #git/#gitlab nötig - und wir sind voll #linux basiert.

#Festanstellung ist das Ziel, #Freischaffend ist weniger gern gesehen..

Bei Interesse: DM an mich.

#fedihire #fedijob

Boosts welcome.


Now that the #Serde issue is resolved by removing the binary, I want to thank @decathorpe again, not only for reporting the issue, but also for all his efforts in the #Rust and #Fedora communities ❤

For others: Please don't call things like this "drama" again. This is pushing back against mistakes that would affect the whole community. I love how much the community cares and that such problems are not ignored 🥰

We are not here to only get things done, we are building a future ❤

#RustLang


Browsed through the projects list on https://gitlab.opencode.de/explore/projects - a #German GitLab instance for the public administration. Chose the https://gitlab.opencode.de/umwelt-info/metadaten because it looked like it could have interesting contents - and found out it uses #RustLang. 🦀


We have some command-line help outputs as well as an example configuration file included in the documentation. In order to prevent these from becoming outdated, we addad a small #RustLang binary crate that updates marked sections in the markdown file. A CI job fails whenever the generated files differ from what is found in the git repository, so the devs are notified about the need to update the documentation in these places. https://gitlab.opencode.de/opentalk/controller/-/tree/main/crates/ci-doc-updater #OpenTalk


@mo8it Worked nicely. Now the only restriction is that the crate which re-exports the macros must not be aliased, but I assume I won't get around that restriction, right? #RustLang


I implemented a #RustLang derive macro that generates code which uses functionality from the serde_derive crate. Drawback: the crate using this derive macro must have serde_derive imported toplevel, and it must not be aliased. How do I properly decouple from that? Is it possible to re-export the dependency in my derive-macro crate? How would I resolve my crate in an absolute manner? It appears $crate is not available in derive macros. #followerpower


We're looking for #RustLang devs at #OpenTalk Backend team. https://opentalk.eu/en/jobs - The code can be found at https://gitlab.opencode.de/opentalk to see whether the technology stack fits.


For writing simple formatted strings in #RustLang, I have these two macros in stdlib available: println!() to stdout or writeln!() to anything that implements the std::io::Write trait. The log crate only contains the equivalent macros to println!(), is there any option to have similar macros that behave like writeln!(), but for the log::Log trait? I know the macros in the log crate are quite involved, and I'd prefer to not ship my own set that simulates their behavior.


Is anybody here extracting #RustLang code coverage as described in https://doc.rust-lang.org/rustc/instrument-coverage.html with https://github.com/mozilla/grcov inside a workspace? I get perfect coverage output for a single non-workspace crate, or for the top-level crate inside a workspace (Cargo.toml having [package] and [workspace] sections). All nested workspace members show zero coverage.


Heute hat #OpenTalk ein in Berliner Rechenzentren gehostetes Cloud-Service mit Bezahltarifen gestartet. Im Backend setzen wir auf #RustLang, das Frontend ist in #TypeScript implementiert. Der Code ist als #FreieSoftware unter #EUPL auf https://gitlab.opencode.de/opentalk verfügbar. Bis auf ein paar wenige Enterprise-Features ist alles im offenen Projekt vorhanden. https://www.heise.de/news/OpenTalk-aus-der-Cloud-Deutsche-Alternative-zu-Zoom-MS-Teams-oder-Webex-9201764.html https://www.spiegel.de/netzwelt/apps/opentalk-deutscher-videotelefonie-anbieter-will-webex-zoom-und-teams-in-behoerden-ersetzen-a-7089489b-aa73-4e0d-bc34-489961bd2b57


The #relm4 project silently released version 0.6.0 without announcement. relm4 is a #RustLang UI library based on #gtk and inspired by #elm. I've been using the 0.6.0 beta for some time now and absolutely enjoy it. https://relm4.org/ https://github.com/Relm4/relm4


Wasmer 3.3 - Running WebAssembly 2.5x faster with JavascriptCore, https://wasmer.io/posts/wasmer-3.3-and-javascriptcore.

Wasmer 3.3 has a new backend which uses JavaScriptCore. Interesting approach. It’s the 4th backend after SinglePass, Cranelift and LLVM.

Wasmer is still a great project but its CEO is a danger. Reminder: https://mnt.io/2021/10/04/i-leave-wasmer/. Its toxic behaviour is still very present.

But the project is great. Thanks to the contributors and the brave employees working there!

#WebAssembly #compiler #runtime #RustLang


Coincidence? 😄
@cloudfest one of the biggest cloud computing conferences (internet infrastructure industry) is happening now in the town of #Rust (Baden-Württemberg, Germany).
@rustlang #rustlang #cpp


Okay? Having used @zellij at work for about a week now I can say it’s really enjoyable to use. Helpful short cut reminders right in the startup ui. No tweaks out of the gate to make it behave sanely. Floating and split panes work great and tabs help me divide up projects. #zellij #RustLang


On my way back from #CLT, I just hopped the ICE train where I had a reserved place at a table of 4 people. Three were already sitting there, doing some coding in #RustLang, so I started talking to them and found out I was sitting there with part of the #slint dev team who were travelling to the #EmbeddedWorld. Nice coincidence, thanks for the nice chat and the stickers, @slint! #CLT2023


#OpenTalk meeting software has finally been released as #FreeSoftware under the EUPL today. I have been part of the #RustLang backend team for a few months now, happy to finally see this happen. One of my tasks was to properly annotate the source code with licensing information, and doing this with https://reuse.software/ has been a great experience. https://gitlab.opencode.de/opentalk https://opentalk.eu/ @OpenTalkMeeting


Watched it live and enjoyed your thoughts on the topic, thank you for that. Can recommend watching to everybody who hasn't seen it. #RustLang #FOSDOM


I've been working with @OpenTalkMeeting purely in rust for a few months now, they are looking for #RustLang devs. My experience with them has been quite pleasant so far. https://opentalk.eu/en/looking-rust-developer


I got the #rust program lsd ( https://crates.io/crates/lsd ) packaged into #debian ( https://packages.debian.org/sid/lsd ). It's my favorite ls replacement.

#rustlang #linux


I'm grateful to lots of people for the hard work they are doing to make this world a better place, and I'd like to show some appreciation. Of course I can't mention everybody, the list is too long and I'd miss many as well. None the less, I'd like to say a big "thank you" to at least a few. Thank you @kattascha @brodnig and @Pia for fighting #conspiracy ideologies. Thank you @liw for giving free #RustLang courses to open source developers. Thank you @debian for processing the #Debian NEW queue.


When I arrive at #FOSDEM, I will probably head straight to #RustLang devroom and stay there the whole day 😉. So many interesting talks announced. https://fosdem.org/2023/schedule/room/h1302_depage/


Have implemented a small #RustLang proc_macro_derive and proc_macro_attribute crate, the use case was replacing macro_rules that looked out of place when being called. From zero to production, this took no more than 3.5h, now all calls to the previous macro have been replaced, looks a lot more idiomatic now. Quite happy about the success, especially because I never implemented macros in Rust before.


I'm amazed by what the #RustLang #mockall crate achieves, but this one little remark to generic methods pretty much prevents a significant portion of the use cases I have for it: "The only restrictions on mocking generic methods are that all generic parameters must be 'static, and generic lifetime parameters are not allowed.". https://docs.rs/mockall/#generic-methods


There are over 100K #RustLang packages!

https://lib.rs/stats
lib.rs screenshot