Eric Hanson

Imo aliasing is basically fine, it just has to be documented. Eg “!!! warning” with “Output may share data with input data” (ideally with exactly when if we can commit...

We could maybe make these docstrings autogenerated if we use inline docstrings in the `@version` invocation, like ```julia @version AnnotationV1 begin "The UUID identifying the recording with which the annotation...

maybe eventually we will get https://github.com/JuliaLang/julia/pull/44381

> I'm assuming the Path constructor has an identity fallback of some sort that would facilitate this? I don't think so... FilePathsBase has a global constant `PATH_TYPES = Type[]` and...

Uhh, I don't totally remember the context but if we still need this then I can try to implement Jarrett's suggestion and proceed with a backport release.

looks like this was done in #89 edit: no, I misunderstood the scope of the issue

We get the paths from `readdir`, I didn’t realize those might not be actual files. Should be easy to fix, is `isfile` the right check?

I guess they could have a directory named `dir.jl` and I shouldn’t `read` that? So maybe `ispath(p) && !isdir(p)` ?

> Is there any idea to handle this situation besides moving all examples to test ? Hm, so PackageAnalyzer only categorizes code as being in test or not in the...

Hm, I think a config could make sense. Do you know if there’s any already existing formats or systems we could use?