Annotations for cross-platform development #7143
Comments
|
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
|
No reaction since this has been submitted so I'd suggest to close, at
least for the moment.
|
|
It does look like a good idea, though. But I would invert the logic: annotate functions that are missing on a given platform. |
|
And use alerts, I guess. |
|
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
Original bug ID: 7143
Reporter: @damiendoligez
Status: acknowledged (set by @shindere on 2017-02-24T15:48:32Z)
Resolution: open
Priority: normal
Severity: feature
Version: 4.03.0+dev / +beta1
Category: platform support (windows, cross-compilation, etc)
Monitored by: @diml @jmeber @hcarty
Bug description
In #5253#c15148, Christophe Troestler wrote:
With the advent of ppx however, I was wondering if, in addition to the documentation, it would not be desirable to introduce a new attribute to say that some function is only on some os_type. An associated warning (turned off by default) would make possible to be sure that a given code does not use functions specific to a given platform (that would also be useful for some external libraries I think).
I think this is a good idea, so I want it to have its own PR, lest it be forgotten.
The text was updated successfully, but these errors were encountered: