aarch64-apple-darwin is now a Tier-2 #rustlang target. You can use it with rustup, cross-compile from x86-64, or compile natively on appropriate hardware! https://t.co/rOb4rntvYR
If you know anyone at @GoogleAds, there's an actively exploited ad bug that obfuscates a malicious link as a legit one.
The google ad ID is DChcSEwjIk--7mtb7AhVU-FEKHZLhCqMYABAAGgJ3cw
Also anyone at @Atlassian, please get the repo taken down.
@JonTDean Make the meetings low key. Our last IRL meetup before the pandemic was weekly at a Panera. Bring a laptop and work on something, or talk to the person next to you, or help them work on something. Big presentations rarely if ever.
@erichdongubler@yaahc_ @ekuber @seritools I actually prefer impl trait in arg position _when it applies_. I think it most matches what people expect (actually would be ok with `foo: SomeTrait` eventually meaning `impl SomeTrait` instead of olde `dyn SomeTrait`). However inline bounds can go to recycle can in the sky.
@yaahc_@rustlang I really want something akin to async’s `join` for errors: run these N things concurrently and wait for them all to succeed or error. If any errored, combine them and bubble up, else get all the success values.
@yaahc_@rustlang Amusingly, a place I’m not happy with Error handling is in the implementation of SNAFU itself. Like others have mentioned, there’s times you want to collect as many errors as possible. https://t.co/PKG0eLyob8
@yaahc_@colinfinck@eugeeeeny@rustlang @ekuber @pnkfelix Perhaps, but that example of anonymous enums would run counter to SNAFU’s principle that an io::Error from opening a file and an io::Error from writing to a socket are semantically dissent. It only allows for a type to be in the enum once.
@shereifHawary I’m not at a computer now, but my gut says that the string allocation can be reduced/avoided. The easy fix is to reuse `input` across calls to `next`. The harder one is removing the string from the split.
I just released SNAFU version 0.7, my #rustlang error definition and creation library. Thanks to hard work from many great contributors, SNAFU now has improved learnability and ergonomics! https://t.co/47OFM4XlBV
@smortimerk@loige Can you describe what’s surprising about it? A few people have been manually doing namespacing like this, but I don’t think anyone has brought up prefixing before.
@loige@smortimerk Make sure to use version 0.7 (currently in beta) as it smooths some rough edges especially felt by new users. https://t.co/iu1G5zoRuS