[wg-camlp4] [Caml-devel] Built-in attributes

[Leo White]

> I don't particularly want to encourage that.  The standard use for [ocaml.warning] I have in mind is to control warnings
> for an entire compilation unit (thus simplifying the build system and making the unit more self-contained), maybe for a
> "section" of it (hence the warning on expressions, to allow begin[@ocaml.warning "..."] .... end), especially during
> development.  It would be a mess if people start to decorate their code with long-lasting warning-tweaking directives
> all over the place, in my opinion.  (Especially from a readability point of view: numbered warnings are quite
> unfriendly.)
>

While this might be true for `[@warning]` it probably won't be true for
every attribute the compiler will understand. I think `[@ocaml.foo]`
could get pretty annoying pretty fast.

Regards,

Leo