- 11 3月, 2015 1 次提交
-
-
由 Jared Parsons 提交于
This is the initial run of the code formatter on the VB compiler source code. Further runs I'll expand on this to include all VB code in a future run.
-
- 10 3月, 2015 2 次提交
-
-
由 Paul Harrington 提交于
-
由 Neal Gafter 提交于
Fixes #1028 Closes #1116
-
- 09 3月, 2015 1 次提交
-
-
由 Jared Parsons 提交于
This change further delays the creation of the PE Stream until the absolute last possible moment.
-
- 08 3月, 2015 3 次提交
-
-
由 Wonseok Chae 提交于
-
由 Wonseok Chae 提交于
VB compiler does not correctly place sequence points in let clause. As a result the debugger does not hit a sequence point set to let clause. Before this fix, we have the following in PDB: <sequencePoints> <entry offset="0x0" hidden="true" document="0"/> <entry offset="0x1" startLine="8" startColumn="25" endLine="8" endColumn="30" document="0"/> </sequencePoints> After having this fix, we have as in Dev12: <sequencePoints> <entry offset="0x0" startLine="8" startColumn="25" endLine="8" endColumn="30" document="0"/> </sequencePoints>
-
由 Adam Becker 提交于
-
- 07 3月, 2015 15 次提交
-
-
由 Wonseok Chae 提交于
-
由 Wonseok Chae 提交于
- Resolve Code review feedback
-
由 Wonseok Chae 提交于
- update comments - update tests
-
由 Wonseok Chae 提交于
-
由 Wonseok Chae 提交于
-
由 Wonseok Chae 提交于
-
由 Wonseok Chae 提交于
-
由 Paul Harrington 提交于
-
由 VSadov 提交于
Fixes #1029 While overall parameterless constructors in structs are valid from IL perspective, without a convenient way to declare them they were virtually nonexistent. As we performed more and more testing, we kept discovering cases where parameterless struct constructors caused inconsistent behavior in libraries or even in some versions of CLR. After reconsidering the potential issues arising from breaking long standing assumptions, we decided it was best for our users to restore the requirement on struct constructors to always have formal parameters.
-
由 Charles Stoner 提交于
-
由 Jared Parsons 提交于
This reverts commit b37052d0.
-
由 Jared Parsons 提交于
This reverts commit 90215346.
-
由 Tomas Matousek 提交于
Use empty array for unspecified public key instead of default(ImmutableArray<byte>) to avoid issues with JSON serialization
-
由 Nick Guerrera 提交于
-
由 Nick Guerrera 提交于
-
- 06 3月, 2015 3 次提交
-
-
由 Tomas Matousek 提交于
Enable hosts to compile strong-named assemblies on all platforms by supplying public key via compilation options and also enable OSS signing with such key
-
由 AdamSpeight2008 提交于
Also tidy up character sequences.
-
由 Paul Harrington 提交于
-
- 05 3月, 2015 3 次提交
-
-
由 AdamSpeight2008 提交于
Using a different implementation, for clarity.
-
由 Matt Warren 提交于
-
由 Matt Warren 提交于
-
- 04 3月, 2015 4 次提交
-
-
由 AdamSpeight2008 提交于
-
由 AdamSpeight2008 提交于
This function encapsulates a common coding pattern in the scanner source. That of a `CanGetCharAtOffset( )` followed by multiple multiple `PeekAheadChar( )` and comparison checks. As a result the scanner source is a bit better to work with.
-
由 Tomas Matousek 提交于
-
由 Neal Gafter 提交于
-
- 03 3月, 2015 4 次提交
-
-
由 Neal Gafter 提交于
-
由 Brett Forsgren 提交于
-
由 Andrew Casey 提交于
The expression compiler returns information to the debugger in the form of .NET assemblies. These assemblies should not contain embedded declarations (i.e. "My.*"). At best, these declarations are useless. At worst, they hide the declarations in the user's own assembly. As a bonus, this fixes an issue we were having with being unable to compile the embedded declarations in cases where two copies of EditorBrowsableAttribute were loaded (since neither is "closer" or more accessible while debugging). Fixes #946.
-
由 Charles Stoner 提交于
-
- 01 3月, 2015 1 次提交
-
-
由 AdamSpeight2008 提交于
-
- 28 2月, 2015 1 次提交
-
-
由 Neal Gafter 提交于
Fixes #223
-
- 27 2月, 2015 2 次提交
-
-
由 Neal Gafter 提交于
Adjust tests for deterministic region analysis Fixes #803
-
由 Jared Parsons 提交于
Add stack guards for the ParseExpression and ParseStatement calls. These are other public entry points into the parser which needed to be guarded in the same way as ParseSyntaxTree. close #839 close #848
-