Skip to content

Conversation

@forki
Copy link
Contributor

@forki forki commented Jan 23, 2018

fixes #4228

image

@forki
Copy link
Contributor Author

forki commented Jan 23, 2018

I used a new error number so that we can built quickfixes on top of it.

@vasily-kirichenko
Copy link
Contributor

Please, add type of the ignored expressing into the warning message.

@forki
Copy link
Contributor Author

forki commented Jan 23, 2018

good point.

image

@vasily-kirichenko
Copy link
Contributor

Excellent, it's in conjunction with the recent Don's PR which added ignored type names into all warning messages.

@forki
Copy link
Contributor Author

forki commented Jan 23, 2018

@dsyme this is weird:

src\fsharp\TypeChecker.fs(847,43): error FS0039: The field, constructor or member 'unitTypeExpectedInSequenceExpression' is not defined. 

for src\buildfromsource\FSharp.Compiler.Private\FSharp.Compiler.Private.fsproj in ci_part3 - but it's clearly there

@forki
Copy link
Contributor Author

forki commented Jan 23, 2018

@vasily-kirichenko @dsyme another question: I see isListTy and isArrayty but no general isSeqTy. Do we have something like that for TType?

@forki
Copy link
Contributor Author

forki commented Jan 23, 2018

@KevinRansom do you see by any chance why CI build 3 does not see the error message?

@KevinRansom
Copy link
Contributor

Probably the way that text is converted to resources is not quite wired up the same. I will take a look later today.

@forki
Copy link
Contributor Author

forki commented Jan 23, 2018 via email

@KevinRansom
Copy link
Contributor

KevinRansom commented Jan 24, 2018

@forki Okay, I pushed a fix.

The reason this happened is because the build failed in the build from source projects. Those guys are for RedHat integration.

That build depends on released product, and the build task that converts from txt file to resx and generates the .fs file is not yet in the build of the dotnet cli that they use. Because of this, we just copy the transformed resx and .fs files. As soon as they update their base build tools we will modify the buildfrom source build to use the buildtask.

Sorry for the inconvenience ...

Kevin

@forki
Copy link
Contributor Author

forki commented Jan 24, 2018

ok cool. so basically I need to touch these 2 files as well and things will be fine?

@KevinRansom
Copy link
Contributor

@forki, yes, until the build from source uses a recent compiler, then it will be automagic like it should be.

@forki
Copy link
Contributor Author

forki commented Jan 24, 2018

ok. this is done.

@cartermp
Copy link
Contributor

cartermp commented Feb 5, 2018

ping @KevinRansom @dsyme for review

@dsyme dsyme merged commit 5c491b2 into dotnet:master Feb 9, 2018
@dsyme
Copy link
Contributor

dsyme commented Feb 9, 2018

Awesome work, thank you

It's possible a similar improvement could be made for async expressions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve warning for ignored values in sequence expressions

5 participants