Localised Compiler Options

[AdamSpeight2008]

Alternative approach to #135

Using Option Strict Off
  ' ...
End Using

[KathleenDollard]

Is the need for a separate partial class in a different file a real pain point for people?

It is TOTALLY cool to just ping an old issue with your comments and that should bubble up to the top.

That's a fine syntax, but I have not thought much about it. I just wonder if other things, like Await in Catch/Finally are bigger pain points.

[Bill-McC]

First of: confused re format of these discussions. Ironic really... is a partial class an issue? Is a partial solution to an issue an issue?
The pain point for me is when I know what kind or kinds of data are coming in, but they aren't "Typed". A block strict off doesn't address that, a dynamic or duck type does

[KathleenDollard]

Yes on discussions. GitHub stinks for discussion, but its what we've got.

I think this issue is somewhat separate from yours because this one is strictly providing Option Strict in a narrower scope. But the separate file seems a hack, but a workaround.

[Bill-McC]

#255 partially addresses my scenario , but not as desirable as #106 or #43. I'm not sure I see the difference between #255 and #117. There's a lot of suggestions around this, and a lot of overlap. Thanks.

[ghost]

@KathleenDollard
Yes it is really a pain, as I need it often for one or two lines of code.
As it is now I have to add a complete partial class or module with a function in it to write those 2 lines.

[KathleenDollard]

@AdamSpeight2008 Can you clarify why this isn't a duplicate of #117. I'd like to close it as a duplicate if it is.