Hi! I am in the latest steps of setting up my repo for publishing and I am now setting up CI. My repo has some symbols declared as public for v1.11+ releases, but I want to keep compatibility in LTS (since there is no a priori incompatibility). I have all my public declarations in a single file (p…

There are the possible solutions of either using the Compat.jl package or using public_declarations = "public x,y,z" VERSION >= v"1.11" && eval(meta.parse(public_declarations)) I cannot test it myself, but maybe it would work if you moved your public.jl file to a directory that is not a subdirecto…

A multiline string holding all the public statements can be iterated over with eachsplit(..., "\n"), allowing eval(Meta.parse(...)) in a loop. Still, the proper thing to do would be not to parse conditionally include-d files when they’re not include-d, but I don’t know the inner workings to know how…

[image] nandoconde: However, in CI, when no coverage is produced for the file, it tries to parse it with JuliaParse, which fails for Julia v1.10. What does this mean? What’s “it”?

See also [image] Is Compat.jl worth it for the `public` keyword? General Usage With the introduction of public by @Lilith , many packages will want to mark their unexported public symbols that way. Since public is only available in Julia 1.11, the current recommended way t…

The codecov action (or whatever generates codecov files in Julia), detects that the file was not included when running Julia v1.10 and thus no codecov file was generated, and attempts to run the Julia parser directly on it to generate it. This is the step that fails. I am away from my PC, but I’ll …

Yeah, I knew about this solution but I prefer to leave it as the last resort, because it is not very aesthetic :frowning:

Oh what am I thinking, we wouldn’t need to iterate a multi-line string and eval(Meta.parse(...)) each line ourselves, include’s underlying include_string(@__MODULE__, ...) is also API. I would still prefer that non-include-d files aren’t parsed by codecov, but the upside of this is you don’t need to…

This is the report from the GitHub Action [image]

Exclude parsing of `public` statements in Julia v1.10 CI

Tooling

gdalle March 16, 2025, 7:19am 5

Topic		Replies	Views
Is Compat.jl worth it for the `public` keyword? General Usage macros , compatibility	37	1545	February 11, 2025
JuliaFormatter, JuliaHub docs, and the public keyword General Usage documenter , juliaformatter	5	306	October 22, 2024
`public` cannot be used when quoting General Usage	1	190	April 8, 2024
What does the new "public" keyword actually do? General Usage question	12	3429	July 23, 2024
V1.11-rc include("") will try to include the current folder Performance release	2	149	August 31, 2024

Exclude parsing of `public` statements in Julia v1.10 CI

Related topics