(1/2) I recently posted a few posts about Rust 🦀 and my intention to leverage it for data science applications. Multiple people asked if Rust is a substitute for R or Python, and the short answer (in my opinion) is no. I see Rust as a complementary or supporting language that could make languages like R and Python faster.
Polaris 🐻❄️ is one example of a Python 🐍 application that uses Rust on the backend. 🧵👇🏼
https://nexte.st/ is awesome. The expression language to filter for tests or simply display a list of available test made is "must-have" for me. #rustlang#rust
I wonder if anyone has ever written an embedded #RDBMS in which there is no run-time #SQL interpreter, and all SQL queries are translated into machine code at compile time.
Kinda like #Rust sqlx, except queries are fully compiled at compile time, not just checked for correct syntax and types.
I'm guessing this would be extremely specific to one #programming language, and outright impossible in most programming languages.
Is this AI generated, or someone thinks middleware aimed for game development is the same as a game engine?
Regardless, can someone help me in finding some kind of #opensource middleware similar to #raylib, #sdl, #sfml, and #glfw? I can't find anything else, especially thanks to #seo and/or people not understanding the difference between engine and middleware. All I need is a fixed buffer audio stream (worst case scenario, I'll use my own that I started writing for my own middleware I can't finish due to lack of time), input handling, and creating an OpenGL window. I don't have enough time to tinker with my own middleware and/or directly hooking into the OS (thanks to SEO, a lot of the search results are also garbage for stuff like rawinput).
"Note that any lifetime bounds, including 'static, apply only to references and types containing references. They do nothing when applied to self-contained types. This means that String is not 'static, but rather it isn't affected by any lifetime bound."
✅ Implemented various challenging Achievements
✅ Implemented game menu
✅ Implemented game over screen
✅ Beautiful new planetary/lunar textures by Björn Jónsson, https://bjj.mmedia.is/data/planetary_maps.html
> Unfortunately, most people seem to have taken the wrong lesson from Rust. They see all of this business with lifetimes and ownership as a dirty mess that Rust has had to adopt because it wanted to avoid garbage collection. But this is completely backwards! Rust adopted rules around shared mutable state and this enabled it to avoid garbage collection. These rules are a good idea regardless.
Yes, so much this! I'm using #Rust not because I'm building low-level resource constrained systems (far from it) but because it allows for local reasoning about state. Paired with the ML inspired syntax that makes pattern matching easy this leads to far more reliable programs.
This is also why I like #Clojure so much. Clojure's refs / atoms /agents allow for scoping mutability in an otherwise purely functional system. Scratch for the same itch. But Rust's compile time checking avoids pushing issues into the runtime, increasing reliability and hugely reduces time needed for debugging. The trade off here is no interactive / live development.
also, now with #gpt4o, latency is going to be critical if you’re doing streaming audio/video, so #python may start looking less appealing. what’s the new #LLM language? #rust? #go? #cpp? #fortran?
i predict that there’s always going to be strong advantages to using #python for #ai, but with streaming audio & video of #gpt4o, there’s not enough latency slack for python.
i think a framework will emerge, similar to pyspark, where you can write python code that gets compiled into a steaming plan, and executed as highly optimized low level #rust code with the possibility of python UDFs. i figure it’s still a couple of years from being really usable rn
I've been moving between neovim, helix (can't get over the slightly different mental model compared to vim), vscode, rustrover... Curious what others use.
I've been helping to investigate a few LLVM and Rust bugs recently, and I keep running into pet peeves with how these bugs are reported, so I'm going to put together some #RulesForBugFiling
I don't want to discourage anyone from filing a bug, please do! But... be aware with how you represent the issue that you're seeing.
I also know that there are folks on here who are vastly more knowledgeable than I am, so feel free to suggest corrections, perhaps by filing some sort of report...
If you're going to claim something is a security issue, please explain what the attacker has gained by exploiting the bug. That is, what they can now do they couldn't before.
The more specific you can be on when a regression occurred, the better. A range of versions is good, a single version is great, a single commit is amazing.
Tools like git bisect are really helpful for this.
Providing a standalone example that reproduces the issue so that someone else can do that work is also great, with the bonus that it can be added to the regression tests.
usually, it is used to define methods, but in function arguments, it serves as syntactic sugar so you don't have to name generic types... but in a return type, it has a meaning that is slightly different, and actually expresses a semantic not even vanilla haskell can represent!
basically, instead of being able to return any type implementing a trait, it states that it can return at least one type that implements a trait.
in haskell terminology, specifying a generic type parameter is "forall a", while returning an "impl" is "exists a".
Second #RustNL result: zlib-rs now works with no_std (on main)
most work was done by fellow unconf attendee Jonas Kruckenberg.
This ability is cool not only because zlib-rs can now be used on embedded devices, but also because it guarantees we don't sneakily use rust's allocator: allocation in the library should only happen through some function pointers that get passed in.