Skip to content

We should disable the --multiemit[+/-] switch in fsi. #17308

Open

Description

@KevinRansom

The internal scenario with a 30 assembly limit is no longer an issue.

It defaults to on anyway.

Activity

  1. added this to the Backlog milestone on Jun 14, 2024
  2. abonie commented on Jun 17, 2024

    @abonie
    Member

    We need to make sure disabling this option does not break anyone

    Vlad says dotnet interactive was using it a year ago

  3. Szer commented on Jul 22, 2024

    @Szer
    Contributor

    It will definitely break a lot of stuff!
    I'm using this option --multiemit- as a workaround for serializers who ignores CompilerGenerated
    Please leave it in FSI 🙏

    #13493
    dotnet/machinelearning#6209

  4. goswinr commented on Feb 19, 2025

    @goswinr
    Contributor

    I am also using --multiemit-, otherwise, I get a type load exception when hosting FSI in Rhino.

    I have not been able to debug the type load exception yet. As a side effect of using --multiemit- i don't have line numbers on Exceptions.

  5. majocha commented on Apr 10, 2025

    @majocha
    Contributor

    It'd be a step in a right direction.
    Let's just make sure the issues mentioned are addressed, and we do have tests for those use cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions