afs commented on issue #1498: URL: https://github.com/apache/jena/issues/1498#issuecomment-1231686298
> Hm, the advantage of PrefixMapping2 is that the internal 'added' map is again a PrefixMapping and the lookup inherts its performance characteristics. There is a `BufferingPrefixMapping` as well. > a solution that can deliver O(log(n)) is appreciated over a O(n) one I don't understand that. `PrefixMapBuffering`, `PrefixMapStd` and `BufferingPrefixMapping` are O(1) prefix lookup. > iri-to-prefix Parsing involves prefix-to-iri. > it's not exhilarating having to clutter my own projects with such rather basic stuff After its many years of evolution, sure Jena does not meet your ideals or the requirements of your day-job, and you can see better ways of of doing things. But Jena is what it is. Open source. Code has to be maintained over years. Code does not get written then remain unchanging. Maintenance work, questions from users, reviewing PRs, releases, security alerts ... rather basic stuff. Just recently, a lot of time has gone into the not-exhilarating work of cleaning up javadoc. Java changed. The javadoc was valid, and now (Java11) it isn't. Jena is not a dumping ground. No volunteer open source project can be. > the problem is not even related to PrefixMapping2 Quite. Did you try the fix? > to avoid @afs from performing a quick fix that seals off the APIs I need Don't make this personal. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
