Skip to content

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

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

Open
KevinRansom opened this issue Jun 14, 2024 · 4 comments
Open

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

KevinRansom opened this issue Jun 14, 2024 · 4 comments

Comments

@KevinRansom
Copy link
Member

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

It defaults to on anyway.

@abonie
Copy link
Member

abonie commented Jun 17, 2024

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

Vlad says dotnet interactive was using it a year ago

@Szer
Copy link
Contributor

Szer commented Jul 22, 2024

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

@goswinr
Copy link
Contributor

goswinr commented Feb 19, 2025

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.

@majocha
Copy link
Contributor

majocha commented Apr 10, 2025

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
Projects
Status: New
Development

No branches or pull requests

5 participants