Skip to main content

i'm not sure why people seem to think #rust error reporting is any good. with #perl, #C or #python, i basically spend no time reading what the error message is actually saying, just quickly identify the faulty line and then quickly to the manual to see what did i get wrong
with rust i just quickly move to a state of misery, because the documentation fucking sucks. there doesn't seem to be no perldoc, man, or pydoc.
does everybody just practice error driven development?
#perl #python #rust #c
in reply to HAMMER SMASHED FILESYSTEM 🇺🇦

Kalamata Hari
Kalamata Hari
• •
i basically spend no time reading what the error message is actually saying


This approach seems bizarre to me regardless of language.

in reply to Kalamata Hari

HAMMER SMASHED FILESYSTEM 🇺🇦
HAMMER SMASHED FILESYSTEM 🇺🇦
• •

@barubary well, it's the same ten errors all over again. i've seen them probably a million times.

if the language's syntax is not too complicated, majority of syntax errors are kind of obvious once compile fails. for the semantic errors, i not consulting the manual, would be a bit more bizarre. but the manual is just so unpleasant to refer to 🙁

@Kalamata Hari
in reply to HAMMER SMASHED FILESYSTEM 🇺🇦

Mo :ferris: :tux:
Mo :ferris: :tux:
• •

What kind of documentation "fucking sucks" or is missing?

What is the problem with documentation in the browser? You can even access it offline.

in reply to Mo :ferris: :tux:

HAMMER SMASHED FILESYSTEM 🇺🇦
HAMMER SMASHED FILESYSTEM 🇺🇦
• •
@mo8it browsers suck, that is not a secret, is it?
switching to a browser when compiling a program in a terminal is an expensive switch. everybody else seems to understand.
also, it's not precisely clear to me how should i switch? i mean, suppose i got the return value of io::std::copy() wrong, what shall i do? so far i've figured rpm -ql rust-doc
| grep std.io.copy
or something, i suppose
perhaps |grep std.*io.*copy
| xargs firefox, i guess?
not difficult to see why man or perldoc are superior
@Mo :ferris: :tux:
in reply to HAMMER SMASHED FILESYSTEM 🇺🇦

Kalamata Hari
Kalamata Hari
• •

@mo8it
OK, this is fascinating to me.

switching to a browser when compiling a program in a terminal is an expensive switch.


I do it all the time; it's just an Alt-Tab away. In what sense is it expensive? Cognitive load, CPU, memory, something else?

(There used to be terminal browsers, too, but I haven't kept up with the state of w3m and lynx.)

As for searching, I haven't used Rust, but https://doc.rust-lang.org/stable/std/index.html?search=std%3A%3Aio%3A%3Acopy looks like a good start. At least in Firefox you could add a bookmark keyword (like "r") for this search field; then it's just a matter of navigating to r std::io::copy. The result list can be navigated with the keyboard (Up/Down for moving between results, Enter for opening the selected result). You can also configure it to automatically open the result if there is only one.

std - Rust

The Rust Standard Library
doc.rust-lang.org
@Mo :ferris: :tux:
⇧