3 Followers
41 Following
68 Posts
Software/Electronics engineer with too many interests to be healthy, including programming, microcontrollers, audio electronics, wine (drinking and producing), honeybees, 3D printing, fountain pens and recently πŸƒπŸ½β€β™‚οΈ

RT @[email protected]

We're adding a fifth string type called "Strang". It's subtly different to String but we're not going to tell you how.

πŸ¦πŸ”—: https://twitter.com/adam_chal/status/1590721811876306944

Adam Chalmers on Twitter

β€œWe're adding a fifth string type called "Strang". It's subtly different to String but we're not going to tell you how.”

Twitter

RT @[email protected]

This is the new Twitter. It isn't great.

πŸ¦πŸ”—: https://twitter.com/jeremy_soller/status/1590788511237828608

Tweet / Twitter

Twitter

RT @[email protected]

"Users could link their online bank account to Twitter,"

I'm gonna stop you RIGHT there

πŸ¦πŸ”—: https://twitter.com/steveklabnik/status/1590432207914827776

steveklabnik on Twitter

β€œ"Users could link their online bank account to Twitter," I'm gonna stop you RIGHT there”

Twitter
Precision vs Accuracy

xkcd

At this year's FOSDEM there is a special dev room dedicated to #rust #rustlang

Check out the website: https://rust-fosdem.github.io/

They're looking for participants and speakers!

@fosdem #fosdem

FOSDEM Rust Devroom

FOSDEM Rust Devroom

The former assumes more structure than the latter, i.e. the latter would happily work if FooBar is a type alias for a collection or primitive. The former makes it more predictable as opinions on error types are encoded. What is the general recommendation or am I looking at it from the wrong position? In the Discord forum people reminded me of `FromStr` trait to formalize a parse function. What do you use? #rustlang
We could see parsing a string into some typed model FooBar as a type conversion from String -> FooBar. Which sounds like what TryFrom-TryInto are made for. However is that recommended practice or is it more usual to just add some function parse(s: &str) -> Result<FooBar> method?
Forgot to add the link,… duh. https://blog.logrocket.com/parsing-in-rust-with-nom/
Parsing in Rust with nom - LogRocket Blog

In this tutorial, we’ll demonstrate how to write a URL parser in Rust using the nom parser combinator library.

LogRocket Blog
A nice blogpost which shows how to parse with *nom*, a parser combinator library for #rustlang . I was considering using it for #adventofcode but maybe overkill?
I made a small tool to scaffold a #rust cargo project and download the personal input for #adventofcode challenges as preparation for next month. Now testing it out on some challenges of previous years.