-
Notifications
You must be signed in to change notification settings - Fork 55
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
Modify portabilities for new Ubuntus #205
base: develop
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #205 +/- ##
===========================================
- Coverage 100.00% 99.99% -0.01%
===========================================
Files 1029 1029
Lines 51386 51377 -9
===========================================
- Hits 51386 51375 -11
- Misses 0 2 +2 ☔ View full report in Codecov by Sentry. |
Following our discussion this morning, I have opened #231 which outlines a strategy for temporarily ignoring (in a very selective and targeted way) some -Wmaybe-uninitialized c_vector warnings. The discussion indicated a preference to temporarily ignore the warnings, with a view to migrating from Boost uBLAS to Eigen in due course, as part of Milestone 2.2. |
I'm stuck on something that appears to be a genuine compiler warning; perhaps something for @jmpf or @mirams: The following line calls
In Chaste/cell_based/src/cell_based_pde/pdes/AveragedSourceEllipticPde.cpp Lines 113 to 118 in 7bf9a4d
What should this specialisation do in the case that the element is null? |
What happens if we assert that it's not null? Does any test-suite fall over? |
Related Issue