Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Include use cases / case studies
See original GitHub issueI think it would be a great addition to the documentation to include user stories or case studies. Like:
“Ben wanted to create a library for Java, but he was afraid other people couldn’t use it because of nominative typing limitations, so he decided to use @structural annotations from the manifold Java library”.
In my case, yes, I am creating a Java library - but I want to make it easy for my users to incorporate the library into their existing code, and structural typing makes that a lot easier as far as I can tell.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I like the idea, it goes along with persona-based marketing themes, which apparently work pretty well. Thanks!
will use this eventually for sure, still working on a library that might need this, but havent got there yet. is there an explanation of how each feature is implemented in this library? maybe write a medium.com article on this lib and link to that article in the readme of the project. if you write a medium article might get more adopters and convince people to use it.