v0.1.0

Changelog

• 0bd2e2b Add a logo and a social preview
• f4a1eef Add types that are not pointers to the return-nil table
• 5546116 Break the unwrap-nil summary and spell the kinds as Go does
• 33da306 Close the gaps the reviews of the specs found
• 9817b5f Drop the work-in-progress warning
• 972feb9 Explain why return-nil and wrap-nil judge a nil slice apart
• 1c1afb3 Head the README with badges, as declscope does
• f22a8a9 Implement the molint rules
• 40b4df9 Implement the return-only rule
• 876c580 Initial commit
• 8e3b368 Lay out the install section as declscope does, with mise first
• f186bf4 Link every mention of samber/mo, samber/lo and nilaway
• 68034f8 Link the rules that other rules refer to
• 4a62cb0 Link the types, functions and methods of mo and lo to their docs
• 13ff295 Make each fix a heading below its rule
• b76c17c Mark the row that another rule reports with a warning
• 8d1544d Mark the rule tables of the README valid or not (#4)
• 5330640 Mark the rules' defaults with green and red
• 5a5e822 Put each rule's fix under its report in the summary table
• 5e3e6ff Rename to molint and pin the rules as fixtures
• 5f19711 Report nil maps, funcs and channels given to mo.Some and mo.Ok
• be59b5d Report nil slices given to mo.Some and mo.Ok
• 004299a Revert "Show how to fix return-nil for each shape of results"
• 8b59c58 Show each fix in the README as code
• 7a4dc03 Show how to fix return-nil for each shape of results
• e02be3f Show the code of each rule's table as a Go block
• 606f7ad Split the README's Valid columns into Valid? and Reason
• cbeb08e Use a value, not a pointer, in the return-error examples
• 98066ba Widen unwrap-nil to every type whose nil breaks on use
• 98d7de3 [Claude] Record how molint and nilaway work together (#3)