Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-nolabels behavior doesn't match documentation #7334

Closed
vicuna opened this issue Aug 26, 2016 · 3 comments
Closed

-nolabels behavior doesn't match documentation #7334

vicuna opened this issue Aug 26, 2016 · 3 comments

Comments

@vicuna
Copy link

vicuna commented Aug 26, 2016

Original bug ID: 7334
Reporter: @let-def
Status: acknowledged (set by @shindere on 2017-02-24T15:40:57Z)
Resolution: open
Priority: low
Severity: feature
Version: 4.03.0
Target version: undecided
Category: typing

Bug description

The manual and the manpages say that in "-nolabels" mode,
"Labels cannot be used in applications".

However it seems that only commuting is forbidden, applications using labels that doesn't need to commute are accepted.

I suggest updating the documentation, I can submit a Github PR if people agree on a better wording.

Steps to reproduce

ocaml -nolabels

let f ~x ~y = x;;

f ~x:() ~y:();;

(* no error, no warning *)

f ~y:() ~x:();;

(* Error: The function applied to this argument has type x:'a -> y:'b -> 'a
This argument cannot be applied with label ~y *)

@vicuna
Copy link
Author

vicuna commented Feb 24, 2017

Comment author: @shindere

Perhaps you could submit a GPR referring to this MPR with an initial wording, so that the discussion can take place there?

@vicuna
Copy link
Author

vicuna commented Mar 14, 2017

Comment author: @garrigue

The -nolabels mode being deprecated, downgrade to feature.

@github-actions
Copy link

github-actions bot commented May 9, 2020

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.

@github-actions github-actions bot added the Stale label May 9, 2020
@garrigue garrigue closed this as completed May 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants