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

printing of types inconsistent with -short-paths #6201

Closed
vicuna opened this issue Oct 3, 2013 · 2 comments
Closed

printing of types inconsistent with -short-paths #6201

vicuna opened this issue Oct 3, 2013 · 2 comments

Comments

@vicuna
Copy link

vicuna commented Oct 3, 2013

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;;

  • : ?buffer_size:int ->
    ?filename:string ->
    in_channel ->
    (Fastq.item, [> Fastq.Error.parsing ]) Core_kernel.Std_kernel._result
    Stream.t
    =

Fastq.in_channel_to_item_stream;;

  • : ?buffer_size:int ->
    ?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.

@vicuna
Copy link
Author

vicuna commented Oct 15, 2017

Comment author: @xavierleroy

What is the status of this PR?

@github-actions
Copy link

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.

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

1 participant