|Anonymous | Login | Signup for a new account||2014-12-22 12:22 CET|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003013||OCaml||OCaml general||public||2004-07-28 06:53||2010-04-30 06:54|
|Target Version||Fixed in Version||3.12.0+dev|
|Description||Full_Name: Evgeny Chukreev|
Submission from: host134.t3n.sotline.ru (184.108.40.206)
In addition to PR#2737.
Another one copy&past killer feature.
Useful becouse 'include' works only with module types, not signatures.
module ExtString :
include (module_type_of_sig String)
val new_value : ...
|Tags||No tags attached.|
|Every so often, I need that feature. The workaround of getting a .mli to be generated by the Makefile and then building a module type from it is, well, messy.|
|I, too, would like to see some feature that allowed me to access/bind the module type of the inferred signature of a module (including module files). I don't think that this would require a new keyword, because it should be clear from the context that the signature is requested.|
|I'll add my voice to those who have encountered this problem before and wished for this feature...|
|I want this feature too. Please.|
|A simpler solution would be to make file.mli generate signature File, or to make things less ambiguous with module, signature FILE|
You wish was granted by Xavier Leroy.
You can write "module type of <module>" since revision 10227.
|2005-11-18 10:13||administrator||New Issue|
|2008-11-14 17:33||Yoric||Note Added: 0004747|
|2008-11-17 23:39||mottl||Note Added: 0004755|
|2008-11-20 18:22||dario||Note Added: 0004771|
|2009-05-27 01:39||jm||Note Added: 0004973|
|2009-05-27 11:27||lavi||Note Added: 0004974|
|2010-04-30 06:54||garrigue||Note Added: 0005423|
|2010-04-30 06:54||garrigue||Status||acknowledged => closed|
|2010-04-30 06:54||garrigue||Resolution||open => fixed|
|2010-04-30 06:54||garrigue||Fixed in Version||=> 3.12.0+dev|
|Copyright © 2000 - 2011 MantisBT Group|