IAP GITLAB

Skip to content
Snippets Groups Projects

Resolve "Need "StackView" object"

Merged Ralf Ulrich requested to merge 106-need-stackview-object into master
1 unresolved thread

Closes #106 (closed)

Edited by Ralf Ulrich

Merge request reports

Pipeline #282 passed

Pipeline passed for 0d3ce93c on 106-need-stackview-object

Merged by Ralf UlrichRalf Ulrich 5 years ago (Feb 5, 2019 8:31am UTC)

Merge details

Pipeline #283 passed

Pipeline passed for 8b7e687e on master

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • 150 150
    151 151 auto const [productionCrossSection, elaCrossSection, numberOfNucleons] =
    152 152 GetCrossSection(corsikaBeamId, targetId, ECoM);
    • It should be possible to add [[maybe_unused]] before auto const to avoid the warning

    • I checked: this does unfortunately not work. The most simple way to "workaround" I found is:

      [[maybe_unused]] const auto& dummy_par = par;

      We could hide this in a Utility macro or so...

    • We could also use std::tie together with std::ignore, see e.g. here. Seems to be much cleaner to me.

    • I have no preference or information about advantages/disadvantages. In general we should not "verkünsteln" us here. We need a decent option, why not the boost::ignore_unused approach? It is very simple and costs nothing.

    • Please register or sign in to reply
    Please register or sign in to reply
    Loading