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.
Reorganization of collections: use inner classes to associate related objects
See original GitHub issueCurrently, we have FooCollection and FooDocument, like ClueWeb09Collection and ClueWeb09Document. Since they are a tightly-bound semantic unit, one could reorganize as inner classes. So:
ClueWeb09would be the name of the collection (implicitly)ClueWeb09.Documentwould be the name of the document from that class.
Same with all the other collections. Then we can reorganize all these bundles in io.anserini.collection.lib; the interface definitions go in io.anserini.collection.
This would also make Javadocs a lot cleaner.
The only major downside I can see is that our source code files will be much longer… but given that one navigates with an IDE these days, it’s not that big a deal…?
Thoughts @Peilin-Yang?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (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
@lintool Jackson uses class definitions of
StatusandWashingtonPostto parse (deserialize & serialize) a tweet JSON and a WashingtonPost JSON data respectively. How about naming themTweetObjectandWashingtonPostObject?Yay, we’re all done. Thanks @borislin !