one thing i am becoming more aware of as i spend more time playing with dotnet stuff after spending so long on rust stuff: rust's culture of documentation is so good. the fact that rust ships a high-quality documentation tool alongside the compiler affects the culture so much
-
Prikaži ovu nit
-
a lot of the time, the closest thing i have to seeing documentation for third-party libraries i use is to load it into Visual Studio and open up Object Browser to pull public items from the library's metadata. this is useful, but documentation it ain't
1 reply 0 proslijeđenih tweetova 15 korisnika označava da im se sviđaPrikaži ovu nit -
there's also the fact that dotnet's documentation comment format is XML-based, whereas rust's is "just markdown", so it's a lot easier to write casually. VS's auto-complete for the doc XML is nice, but being able to Just Write Shit is far less friction
0 proslijeđenih tweetova 20 korisnika označava da im se sviđaPrikaži ovu nit -
in short, this is the background i had when i got into rust, and why i spent so much energy making rustdoc as good as i could. i saw what happened when you didn't have a culture of documentation, and i wanted to ensure that i could make writing docs for rust way easier
0 proslijeđenih tweetova 29 korisnika označava da im se sviđaPrikaži ovu nit
nice (i wasn't expecting this to do numbers but i'm glad people appreciate it, lol)pic.twitter.com/duc24sMB8F
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.