cider 2021-01-02 | Slack Archive

vemv14:01:24

> On some days I'm wondering if I should just drop everything Java-related as it's such a pain in the ass. Hope it's tongue-in-cheek ;p especially as I'm set out to solve https://github.com/clojure-emacs/cider-nrepl/issues/64 (see the last post) As a semi-related idea, if javadocs in particular are a PITA, one could indeed drop them, as they are strictly a subset of java sources. I see Orchard already does some Java source parsing. There's the com.github.javaparser package as well which might be particuarly stable

bozhidar15:01:47

@vemv Our parser is much simpler than GitHub's - we don't really need an AST for Java sources or something like this. Orchard's Java parser extracts only the data we need for the info functionality (source locations, JavaDoc, etc).

vemv15:01:31

for clarity, I was talking about https://javaparser.org/ which artifact, oddly enough is prefixed com.github

vemv15:01:38

what I had in mind is - you don't need javadoc if one does a simple parsing of a single source file. you get exactly the same info a javadoc would give you, right?

bozhidar08:01:19

Yeah, that's true. The only downside would be the need for a third-party dep. Part of the reason we've opted for our simpler approach is to avoid having any deps in Orchard.

vemv11:01:37

yeah a java dep doesn't sound mranderson-able :)

bozhidar15:01:35

It actually handles those, but Orchard doesn't use mranderson, only cider-nrepl does. And the info functionality for Clojure, Java and ClojureScript happens to live in Orchard currently.

👀 3

bozhidar15:01:04

(and it's the thing that got broken by some changes in Java 15)

2021-01-02

Channels