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
{{ message }}
Repository navigation
occasionally unhelpful behavior of toplevel when printing values #7751
Original bug ID: 7751 Reporter: kosik Assigned to:@garrigue Status: confirmed (set by @garrigue on 2018-03-13T02:37:04Z) Resolution: open Priority: normal Severity: minor Version: 4.06.1 Category: toplevel Related to:#7134 Monitored by:@nojb
The problem (in my opinion) is that some of the values are printed as
<abstr>
even if they are not abstract and the corresponding *.cmi files (which describes their structure) is available. For some reason, Ocaml toplevel chooses not to process them.
I find this behavior surprising (at least).
It certainly also is an undocumented behavior.
Related surprising behavior is that when I install printers for those values that are printed as <abstr>, those printers will not be used
(just because that Ocaml toplevel chooses (for an unknown reason) not to process relevant *.cmi files.
Interestingly, if I make some dummy calls of functions in some of the modules that Ocaml toplevel (temporarily) avoided to process, it processes them lazily and then the printing procedures behave in an expected manner.
Activity
vicuna commentedon Mar 12, 2018
Comment author: kosik
Sorry, the title should read:
"occasionally unhelpful behavior of Ocaml toplevel when printing values
vicuna commentedon Mar 13, 2018
Comment author: @garrigue
I observe the same behavior with
vicuna commentedon Mar 13, 2018
Comment author: @garrigue
Apparently the culprit is the fix of #7134, which blocked the loading of cmis.
A tentative fix is at: #1657
yallop commentedon Apr 15, 2019
This appears to be fixed in 4.07.1: