Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@Hixie
Copy link
Contributor

@Hixie Hixie commented Aug 21, 2015

Fixes #698 to actually work.
Also, adds some debugging aids around Flex.
And a test to check this fix.

Fixes flutter#698 to actually work.
Also, adds some debugging aids around Flex.
And a test to check this fix.
@abarth
Copy link
Contributor

abarth commented Aug 21, 2015

LGTM

@Hixie
Copy link
Contributor Author

Hixie commented Aug 22, 2015

The test failure (CC @abarth) seems unrelated (and I didn't hit it when developing?), so I'm merging this in.

Hixie added a commit that referenced this pull request Aug 22, 2015
Reimplement 'stretch' for flexible items correctly.
@Hixie Hixie merged commit 15a1132 into flutter:master Aug 22, 2015
@Hixie Hixie deleted the flex-bug branch August 22, 2015 03:05
@abarth
Copy link
Contributor

abarth commented Aug 22, 2015

I think it's an issue with the new harness being flaky. :(

@eseidel
Copy link
Contributor

eseidel commented Aug 22, 2015

Thank you!

rhencke pushed a commit to rhencke/engine that referenced this pull request Dec 20, 2020
rhencke pushed a commit to rhencke/engine that referenced this pull request Dec 20, 2020
Remove misleading wording in VkDescriptorBufferInfo::buffer comment
qadevices pushed a commit to qadevices/engine that referenced this pull request Oct 3, 2023
The Clang 18 roll here flutter#45486 will
add a new warning like:

we get errors of the form:
```
../../third_party/json/include\nlohmann/json.hpp(5142,35): error: identifier '_json' preceded by whitespace in a literal operator declaration is deprecated [-Werror,-Wdeprecated-literal-operator]
 5142 | inline nlohmann::json operator "" _json(const char* s, std::size_t n)
      |                       ~~~~~~~~~~~~^~~~~
      |                       operator""_json
```

That is, Clang rejects `operator "" _a` unless spaces are removed. This
PR adds a flag to silence the warning util it is fixed upstream.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants