I think the solution, at least from a social perspective, is to make authoring a blog or tutorial which includes all the appropriate package names easier than authoring a blog or tutorial which omits them.https://twitter.com/propensive/status/1201177788247683072 …
-
Show this thread
-
How could that possibly be? Well, nobody writes examples without doing some form of checking on them. Having a compiler check the examples is already easier than compiling them (reliably) in your head, and it forces you to provide all necessary context.
3 replies 0 retweets 1 likeShow this thread -
So, to be easier overall, it "just" needs to be made easy to check the code fragments embedded within some text (in whatever form), without forcing the author to jump through too many hoops to set everything up. I have a background process running in my brain working on this.
3 replies 0 retweets 2 likesShow this thread -
-
-
-
-
Replying to @noelwelsh
I'm envisaging something much easier than that, just because I don't want people to have to set up a project in order to write docs. I'm thinking or can be done with just a single line which specifies everything. Maybe that line contains a hash copied from somewhere... ;)
1 reply 0 retweets 0 likes
Though I should get implementing this already... ;)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
I just use it from sbt