HNHacker News
TopNewBestAskShowJobs

schubart

79 karma · joined July 26, 2020

submissionscomments
schubart··on Iranian Officials Asking Venezuela for Asylum in Case of Regime Change
Former East German leader Erich Honecker [1] lived in Chile until he died of cancer.

[1] https://en.wikipedia.org/wiki/Erich_Honecker

schubart··on Show HN: A robot that plays the Simon game
Thanks! The two imported crates provide the interface to the hardware (servos and sensors), so they don't add much abstraction. Most abstraction is in `robot.rs`, so that `main.rs` is clean and high-level.

Without `rustfmt::skip`, rustfmt would break these sections into more lines but I prefer them to look like little tables.

schubart··on Multiple assertions are fine in a unit test
> On the one hand, running tests in any order should produce the same result, and would in any decent test suite.

Therefore the tool should run the tests in random order, to flush out the non-decent tests. IMHO.

schubart··on Feelings of guilt may signal leadership potential (2012)
What does "SV" stand for?
schubart··on Ask HN: What podcasts are you listening to?
I could not find any podcast called “History of Napoleon”. Did you perhaps mean “The Age of Napoleon”?

https://ageofnapoleon.com/

schubart··on Using unwrap() in Rust is okay
> When checking preconditions, make sure the panic message relates to the documented precondition, perhaps by adding a custom message. For example,

> `assert!(!xs.is_empty(), "expected parameter 'xs' to be non-empty")`.

This panics with

> thread 'main' panicked at 'expected parameter 'xs' to be non-empty', src/main.rs:79:5

Without the custom message it's

> thread 'main' panicked at 'assertion failed: !xs.is_empty()', src/main.rs:79:5

Given that panics should be for bugs, i.e. interpreted by developers, I'd say the second message is clear enough and a custom message just adds noise in the source code.

schubart··on Mundane chores are all the rage in gaming
You might enjoy unclogging:

https://youtube.com/watch?v=1-zEvy3BaUw

schubart··on Google's Subsea Fiber Optics
> A message took over 17 hours to deliver, at 2 minutes and 5 seconds per letter by Morse code

A letter in Morse code is made of up to four “dits” or “dahs”. Why would it take more than two minutes to send one letter?

schubart··on A work-in-progress Magit clone for Neovim
https://github.com/TimUntersberger/neogit/pull/159
← PreviousPage 2 of 2