-
Notifications
You must be signed in to change notification settings - Fork 231
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
Set warnings to be always printed #3370
Conversation
I think the |
LOL there are 53630 MaybeQuotedTT warnings and 5652 others XD
Fun fact: out of 6683 examples in M2, the average takes about 2.8s, standard variation is ~5.3, and the top 10 take 15 minutes! I'm thinking of adding a warning for examples taking more than 30s, which is only about 28 examples taking 28 minutes. The example for lowerBound in SumsOfSquares takes more than 4 minutes! Similarly, out of 4008 tests, average is 0.85s, std.var is ~2.8, but only 7 or so take more than 30s. Maybe a warning there isn't a terrible idea. Surprisingly all tests are under a minute. |
9520063
to
5c94d17
Compare
Rebased this on top of the qname changes. Hopefully there should be very few warnings now. |
5c94d17
to
ef722d5
Compare
ef722d5
to
07aff82
Compare
Is this good to merge? |
e444b2f
to
ae73772
Compare
I think so. I'll go ahead and merge #3376 first since this is on top of that. |
401d368
to
d40887f
Compare
d40887f
to
803dc5b
Compare
Before:
After:
My intention is to force users to cut short their documentation headlines, but I'm not sure what those markup type warnings are all about ...