Skip to content

Conversation

@ggoossen
Copy link
Contributor

@ggoossen ggoossen commented Nov 5, 2019

Stack from ghstack:

Previous attempt in #28616 didn't work in clang8 and got reverted in #28916
This one escapes the } inside the brackets, maybe that works

Differential Revision: D18324286

…attempt

Previous attempt in #28616 didn't work in clang8 and got reverted in #28916
This one escapes the } inside the brackets, maybe that works

Differential Revision: [D18324286](https://our.internmc.facebook.com/intern/diff/D18324286/)

[ghstack-poisoned]
@ggoossen ggoossen requested a review from apaszke as a code owner November 5, 2019 12:24
@facebook-github-bot facebook-github-bot added the oncall: jit Add this issue/PR to JIT oncall triage queue label Nov 5, 2019
ggoossen added a commit that referenced this pull request Nov 5, 2019
…attempt

Previous attempt in #28616 didn't work in clang8 and got reverted in #28916
This one escapes the } inside the brackets, maybe that works

Differential Revision: [D18324286](https://our.internmc.facebook.com/intern/diff/D18324286/)

ghstack-source-id: 93270628
Pull Request resolved: #29193
…ns, second attempt"

Previous attempt in #28616 didn't work in clang8 and got reverted in #28916
This one escapes the } inside the brackets, maybe that works

Differential Revision: [D18324286](https://our.internmc.facebook.com/intern/diff/D18324286/)

[ghstack-poisoned]
ggoossen added a commit that referenced this pull request Nov 5, 2019
…attempt

Pull Request resolved: #29193

Previous attempt in #28616 didn't work in clang8 and got reverted in #28916
This one escapes the } inside the brackets, maybe that works
ghstack-source-id: 93283014

Differential Revision: [D18324286](https://our.internmc.facebook.com/intern/diff/D18324286/)
@ggoossen
Copy link
Contributor Author

ggoossen commented Nov 6, 2019

cc @jamesr66a

@ggoossen ggoossen requested a review from jamesr66a November 6, 2019 12:53
Copy link
Collaborator

@jamesr66a jamesr66a left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried a bunch of escaping, including this one and it didn’t work. The issue is it’s throwing an error about square brackets, not braces, but the square brackets are well formed anyway so the standard library just seems broken.

Like I said ok the other PR, we should be able to get the desired behavior by just using a one or more match (+) with a non-greedy search(?). I don’t think we need to explicitly exclude closed braces

@ggoossen
Copy link
Contributor Author

ggoossen commented Nov 6, 2019

@jamesr66a That won't work with multiple format arguments as it will match the opening { of the first {} with the closing } of the second {}
Maybe we should use a regex and instead just search for { and check the next character.

@ggoossen ggoossen closed this Nov 6, 2019
@jamesr66a
Copy link
Collaborator

@ggoossen that's not the case if you use a non-greedy match (the question mark token)

@facebook-github-bot facebook-github-bot deleted the gh/ggoossen/3/head branch December 7, 2019 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

oncall: jit Add this issue/PR to JIT oncall triage queue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants