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: 6201 Reporter: Ashish_Agarwal Status: acknowledged (set by @lpw25 on 2018-01-29T16:40:21Z) Resolution: open Priority: normal Severity: minor Version: 4.01.0 Category: typing Monitored by:@hcarty
Bug description
When the toplevel is started with -short-paths, the style in which a type is printed changes from the first printing of a type to all successive printings.
The first time we get Fastq.item and the second time we get Biocaml_fastq.item. The latter style then remains for all subsequent invocations. It is not necessary to call the same function both times. The style changes permanently regardless of what value is being executed.
Maybe of relevance: the Biocaml module is a manual pack, i.e. it contains definitions like `module Fastq = Biocaml_fastq". I do not see the above behavior in Core, which uses -pack.
The text was updated successfully, but these errors were encountered:
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: 6201
Reporter: Ashish_Agarwal
Status: acknowledged (set by @lpw25 on 2018-01-29T16:40:21Z)
Resolution: open
Priority: normal
Severity: minor
Version: 4.01.0
Category: typing
Monitored by: @hcarty
Bug description
When the toplevel is started with -short-paths, the style in which a type is printed changes from the first printing of a type to all successive printings.
Steps to reproduce
$ ocaml -short-paths
#require "biocaml"
open Biocaml
Fastq.in_channel_to_item_stream;;
?filename:string ->
in_channel ->
(Fastq.item, [> Fastq.Error.parsing ]) Core_kernel.Std_kernel._result
Stream.t
=
Fastq.in_channel_to_item_stream;;
?filename:string ->
in_channel ->
(Biocaml_fastq.item, [> Fastq.Error.parsing ])
Core_kernel.Std_kernel._result Stream.t
=
The first time we get Fastq.item and the second time we get Biocaml_fastq.item. The latter style then remains for all subsequent invocations. It is not necessary to call the same function both times. The style changes permanently regardless of what value is being executed.
Maybe of relevance: the Biocaml module is a manual pack, i.e. it contains definitions like `module Fastq = Biocaml_fastq". I do not see the above behavior in Core, which uses -pack.
The text was updated successfully, but these errors were encountered: