Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change TastyFormat for REFINEDtype to conform to existing .tasty files #13507

Merged
merged 1 commit into from Sep 13, 2021

Conversation

cache-nez
Copy link
Contributor

In TASTy files created by TreePickler, the order is name-type-type. Reflect this in the grammar.

Closes #13506.

In TASTy files created by TreePickler, the order is name-type-type. Reflect this in the grammar.
@cache-nez
Copy link
Contributor Author

image
I can't sign the CLA, anything better to do than going through Contact Us?

@smarter
Copy link
Member

smarter commented Sep 10, 2021

I can't sign the CLA, anything better to do than going through Contact Us?

Not sure what can be done except refreshing the page, I don't know who maintains the cla check /cc @SethTisue

@SethTisue
Copy link
Member

SethTisue commented Sep 13, 2021

@JustinPihony could your team look into this...? did some configuration on Lightbend's end change recently?

I get the same error if I try to sign the Scala CLA myself

@JustinPihony
Copy link

@cache-nez Please try to sign the CLA now. I have fixed the bug and verified internally. If you run into any further problems let me know.

@cache-nez
Copy link
Contributor Author

@JustinPihony thank you, it worked perfectly now!

@bishabosha bishabosha merged commit bd214f1 into scala:master Sep 13, 2021
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.

REFINEDtype rhs in TASTy format does not correspond to reality
6 participants