NireBryce

reality is the battlefield

the first line goes in Cohost embeds

🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮

I speak to the universe and it speaks back, in it's own way.

mastodon

email: contact at breadthcharge dot net

I live on the northeast coast of the US.

'non-functional programmer'. 'far left'.

conceptual midwife.

https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut

If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.


it uses :quit so you're like
exit

error[E0425]: cannot find value `exit` in this scope
 --> src/main.rs:4:1
[...]
help: consider importing this function:
use std::process::exit;

exit()

error[E0425]: cannot find function `exit` in this scope
 --> src/main.rs:4:1
[...]
help: consider importing this function:
use std::process::exit;

use std::process::exit;
exit()

error[E0277]: `fn(i32) -> ! {exit}` doesn't implement `Debug`

quit

error[E0425]: cannot find value `quit` in this scope

help

error[E0425]: cannot find value `quit` in this scope

help()

error[E0425]: cannot find function `help` in this scope

ctrl-z
   ~  ddgr "irust" quit
   ~  fg
:quit


You must log in to comment.

in reply to @NireBryce's post:

i think if your program does some cutesy shit when reading empty you should be shot. (and unless you're using libreadline, same applies if it does some cutesy shit when getting intr). this opinion brought to you by gnu bc which (at least used to on bullseye) correctly understand EOF until you sent it intr at which point it would just say "(interrupt) use quit to exit." and the only way to exit it was either typing in literal quit or sending it quit