Unless I am missing on something, right now if you #load "something.fsx" in a fsi.exe session, you cannot interactively use the functions in that script file (loaded, signatures displayed but not accessible, somehow).
If, on the other hand I open a cmd.exe, then start "fsi.exe --use:something.fsx" I can use those types out of the box as if Ihad ALT-ENTERED it to f# interactive from within VS.
So, adding a #use which creates the same behavior as "fsi.exe -- use:" seems to be a good idea to me.1 vote
1、new line's first word can not list members automaticly,i need use ctrl+J,but c# or vb works fine,even python works better than F#(MS's natural son)
2、 i define a new expression on the top,but intellisense can't auto list it,crtl+J again,even python can do it.
Sad(ಥ _ ಥ)1 vote
I find F# syntax coloring lacking with vs2013 default settings. It's mostly a few bits of blue and rest white text.
ex. following lines are nearly all white text.
let flattenRanges overallMin overallMax (comparer:System.Collections.Generic.IComparer<_>) ranges =
let f = Expression.Lambda<Func<seq<OptionalValue<obj>>, IVector>>(body, par).Compile()
member x.SelectOptional<'R>(f:System.Func<KeyValuePair<'K, OptionalValue<'V>>, OptionalValue<'R>>) =
let newVector =
index.Mappings |> Array.ofSeq |> Array.map (fun (KeyValue(key, addr)) ->
let newIndex = indexBuilder.Project(index)
Series<'K, 'R>(newIndex, vectorBuilder.CreateMissing(newVector), vectorBuilder, indexBuilder)0 votes
- Don't see your idea?