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
Original bug ID: 1691 Reporter: administrator Status: closed (set by @damiendoligez on 2008-01-22T13:17:26Z) Resolution: fixed Priority: normal Severity: feature Fixed in version: 3.09.0 Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Wheeler Ruml
Version: 3.06
OS: linux and mingw
Submission from: katsura.parc.xerox.com (13.2.18.21)
Tiny suggestion: how about an optional warning for variables that are bound but
never used elsewhere? For me, at least, this often signals a programming error
(analogous to implicitly ignoring a return value). Perhaps this would apply
only to bindings inside another let, but looking at the .cmi should allow one to
tell whether a toplevel binding could possibly be used by another module.
Just a thought. Thanks for some great software!
Wheeler
The text was updated successfully, but these errors were encountered:
Original bug ID: 1691
Reporter: administrator
Status: closed (set by @damiendoligez on 2008-01-22T13:17:26Z)
Resolution: fixed
Priority: normal
Severity: feature
Fixed in version: 3.09.0
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Wheeler Ruml
Version: 3.06
OS: linux and mingw
Submission from: katsura.parc.xerox.com (13.2.18.21)
Tiny suggestion: how about an optional warning for variables that are bound but
never used elsewhere? For me, at least, this often signals a programming error
(analogous to implicitly ignoring a return value). Perhaps this would apply
only to bindings inside another let, but looking at the .cmi should allow one to
tell whether a toplevel binding could possibly be used by another module.
Just a thought. Thanks for some great software!
Wheeler
The text was updated successfully, but these errors were encountered: