@ElAfalw please always show a minimal reproducible example to help others.
I've encountered similar issues.
(from memory, please correct if wrong) for better of for worse, notes (warnings
and hints) have a notion of:
* foreign package notes (eg: stdlib, 3rd party packages)
* main package notes (whatever modules belong to the same package as main
module)
notes (apart from `--hints:off` IIRC) typically control only main package notes.
If you want to improve situation, you can start looking at this code snippet in
nim repo:
graph.config.notes =
if s.getnimblePkgId == graph.config.mainPackageId or
isDefined(graph.config, "booting"): graph.config.mainPackageNotes
else: graph.config.foreignPackageNotes
Run
the question is, what should be desired semantics, and should there be options
to operate on "all notes" instead of just main package notes
