Gauthier Segay

@dsyme, could you expand on "implementation cost quite high", giving pointers about implications on the IL code gen being more involved? I think suggestions like this shouldn't be closed, but...

Also, it seems antithetical to https://twitter.com/dsymetweets/status/1224739090253467648 to relinquish this without giving pointers, and directing arrows that would dereference the implementation in the compiler.

there is also this edge case https://github.com/dotnet/fsharp/issues/15780 for fluent notation that currently prevents method and arguments to be separate.

FSharp.Stats? > get pressure from the SDK team to become an optional install feature because of our size and relatively small user base It is not because F# is "small...

@cr3wdayt5p thanks for the extensive and detailed bug report. I'll try to investigate it, you can also check if the issue is the same with the dotnet framework, if you...

@cr3wdayt5p thanks for additional details. You may bring your own feedback on those issues, or try to open specific one, asking about native dependency loading in context of type providers...

@daniellittledev, thanks for the report, with the stacktrace, we know the issue surfaced from this: https://github.com/fsprojects/FSharp.Data.SqlClient/blob/712b8cb1b00389d7ad6564b09da0638a0a39e0d3/src/SqlClient/ISqlCommand.fs#L374 Can you update us with your intuition if this is a case of SQL...

@sachinshahredmane, this isn't achievable, the SQL parser itself wouldn't accept the statement. What you can do, is have `like @logTblName` in your statement, and put the patterns (and escape `%`)...

@daniellittledev I've tried to reproduce the issue in #425 but the added test doesn't throw a SqlException, do you mind trying it out and adjust the test accordingly to reproduce...

@sgryt thanks for the report. From what I understand, it is more likely to be a dotnet/sdk issue or (maybe) dotnet/fsharp one, there is nothing in the `FSharp.Data.SqlClient` nuget package...