-
Notifications
You must be signed in to change notification settings - Fork 789
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
Problems using FSI on multiple namespaces in a single file #237
Comments
To clarify - repro is to put the above code in |
Yes, sorry, thanks for the clarification. |
Hi - appreciate that there's other bugs out there that need squashing - just wondering if this one is penned in for fixing as part of the F#4 release? It's a real issue that is affecting is with a production system here in that we can't using .fsx files with our current codebase. Not complaining if it's not - just wondering on how far up the priority list it is :-) |
I don't think anyone is looking at this one with any higher priority than any others. FWIW I have a really terrible workaround for you, which actually probably points to the root cause. Seems the fake namespace Foo
type Name = Name of string
namespace Bar
#if INTERACTIVE
open FSI_0001.Foo
#else
open Foo
#endif
type Person = Person of Name |
@isaacabraham - I've prepared a fix for this here: #359 |
Awesome :-) I was trying to work around that today so am looking forward to this! |
Somewhat related to #44. The following single (valid) .fs file with the following two dependent namespaces will not compile in FSI:
with the error
There doesn't seem to be a workaround for this - with #44 you could work around it within the .fsx by manually adding
open
statements.The text was updated successfully, but these errors were encountered: