Error Prone VS GitHub Gist

A special kind of validation is enforcing that record fields are not null. (Un)fortunately, records do not have any special behavior regarding nullability. You can use tools like NullAway or Error Prone to prevent null in your code in general, or you can add checks to your records:. - Source: dev.to / over 1 year ago

I am all in favour to more third side libraries adding functionalities, like Lombok, Manifold and error prone. As well as smaller projects like this shameless plug and what appears in this list. Source: over 1 year ago

While at it you could also point them to static code analyzers such as error_prone, spotbugs and pmd (use all 3 at once - they complement each other in detecting different issues). Source: over 2 years ago

Linters can check for this sort of thing, for example Error Prone[0] has a lint[1] for this. Totally agree this is better to be in the language proper so we don't need this extra tooling. [0]: https://errorprone.info [1]: https://errorprone.info/bugpattern/ParameterName. - Source: Hacker News / over 2 years ago

If you are learning things, you could also create github gists. That way your repos will only be coding related, while you can create tutorials / work exercises in gists. Source: over 1 year ago

I use Github, both for full repos and for short gists. Source: about 2 years ago

On the other hand, shared DartPads are just gists on GitHub so theoretically they can include code that works with different packages. Of course, such gists will not compile in DartPad and will be displayed as having errors :(. Source: over 2 years ago

Perhaps github gists? https://gist.github.com/discover. Source: over 2 years ago

I looked at Github gists, but they are focused in displaying the markdown sourcecode (so e.g. Hyperlinks won't be clickable [1] ). Options just don't seem to be focused on simply hosting PDFs/information with clickable references. Source: over 2 years ago