You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per https://github.com/inko-lang/inko/actions/runs/14242327365/job/39915164284 we're not taking into account conditional compilation tags when generating JSON documentation files, and instead just generate documentation for all modules. This results in CI failing because std.int.release implements types also implemented in std.int.debug.
Operating system
Arch Linux
Inko version
main
The text was updated successfully, but these errors were encountered:
There's a bit of a problem with this approach: for libraries there's no clear "entry point", i.e. it could be src/foo.inko or src/whatever/bla.inko, such that the only option is to include all modules.
For the current failures I think what we can do is to keep the implementations in std.int but forward them to module methods defined in std.int.debug and std.int.release, similar to the std.sys setup used for other modules.
Please describe the bug
Per https://github.com/inko-lang/inko/actions/runs/14242327365/job/39915164284 we're not taking into account conditional compilation tags when generating JSON documentation files, and instead just generate documentation for all modules. This results in CI failing because
std.int.release
implements types also implemented instd.int.debug
.Operating system
Arch Linux
Inko version
main
The text was updated successfully, but these errors were encountered: