u/davebrk

I'd recommend another combination that I like, `derive_more::Error` + `anyhow::Result`.

https://docs.rs/derive_more/latest/derive_more/derive.Error.html
https://docs.rs/anyhow/latest/anyhow/type.Result.html

I'm looking to replace usage of curl where we reuse the buffer between calls (and we make a lot of them, and try to allocate all upfront, when we can).

Awesome! Thanks.

And for the second case, replacing the data in the buffer between requests without allocating new memory?

Does it support reusing the request body, if I want to perform the same request multiple times? Or if I want to use the same buffer for performing multiple requests serially, instead of allocating anew for each request.

If the changes are small it's because it's already a very mature project. And one I prefer over RustRover, though I have a license for that too.

Thanks! It works very well. I already found a failing test.

Really nice!

Do note that it requires using nightly. Otherwise I get the following error:

Preparing a careful sysroot (target: aarch64-apple-darwin)... thread 'main' panicked at 'failed to build sysroot; run `cargo careful setup` to see what went wrong: sysroot build failed', /Users/xxx/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-careful-0.2.1/src/main.rs:194:10

Instead run with cargo +nightly careful test.

This is a good Slack api that I've used before: https://docs.rs/slack-morphism.

I think Niko was the one who introduced the borrow checker concept to Rust. His influence is felt in many many technical decisions, and even more so in his leadership style, which you could read back then (I don't if it's still available, but there use to be irc logs, github summaries of meetings, I'd feel a bit like a stalker, but it was very interesting, seeing how the sausage was made, so to speak).

Rust certainly would not be the same without him, and I personally wish he'd never leave the Rust project.

It it usually very very good, but sometimes it just does not work.

One example is when writing code that is wrapped in a macro. Whether in an #[async_trait] impl block, or #[tokio::test] function, then inside auto complete does not work for me, and on any small wrong change, the complete function/block will be underlined in red, which is distracting.

Another problem (not sure if rust-analyzer's) is that for tests that are again inside a macro such as #[tokio::test], failure in the test will up on an incorrect, sometimes not existent, line number.

In spite of all of this, rust-analyzer is amazing. I've a paid licence of Clion, and nonetheless I still mostly use vscode with rust-analyzer. I'm really thankful to its developers.

Within #[tokio::test] function it does not work for me.

What about httpx?

Does it also supports aligned PER? Any plans for it?

ASN1 APER library for decoding & encoding.

For a moment I had hope.. but no APER codec support :(.

Still very nice!

Yes this it it! Thanks!

Thanks for the livestream.

I have a frivolous question. What's is the font type in the rust code slides now? It is beautiful.

Thanks. I think this is it: Reaching const evaluation singularity.

I think you might be able to build a REPL out of it too.

Let's say I'm interested in pitching in for this, though I'm not sure I have the knowledge/experience. Where should I look in the code/read?

I also looked to buy some rust cups for work, but could not find good ones.

Thanks. Ordered 2.

Only Europe?

Found some explanation: https://www.reddit.com/r/Teespring/comments/2odozy/whats_the_difference_between_a_hanes_tagless_tee/

I'm not familiar with all the different types of t-shirts there is.. of the short sleeves type listed, is there a difference in quality? or is it just the style?