Rust

Maybe a good idea for a post. But the amount of reaches required makes this icky.

• Pretending people write:

  let Ok(x) = read_input() else { return Err(Error) };
  

  instead of

   let x = read_input().map_err(|_| ...)?;
  

• Pretending people write:

   const x: &str = "...";
  

  instead of

   const X: &str = "...";
  

• Pretending there exist people who have such knowledge of rust macros hygiene, ident namespaces, etc, but somehow don't know about how macro code expands (the "shock" about the compile error).

Maybe there is a reason after all why almost no one (maybe no one, period) was ever in that situation.

This was a great post, but is the last state of the macro actually bad for performance in any way? I get that it's ugly (and we should only choose to make code less readable like this when there's actually an issue) but is it worse for runtime performance?

That was such a cute lil post