Yanzhao Wang （王彦昭）

> This is another bug that shouldn't be in the list: > > FilePath: /__w/R3BRoot/R3BRoot/r3bdata/footData/R3BFootHitData.cxx Message: '''Int_t'' and ''Double_t'' may be implicitly converted: ''Int_t'' (as ''int'') -> ''Double_t'' (as ''double''),...

> > > Usually these parameters are defined in-flight taking the right values from parameter containers, so the initial value is redundant. > > > > > > Could you...

> > > > > Usually these parameters are defined in-flight taking the right values from parameter containers, so the initial value is redundant. > > > > > >...

Like I said in the last R3B analysis meeting, **clang-tidy only checks the changed code**. It WILL NOT give any warnings on existing code. > This code is nothing new....

>I think that this problem was solved in 5min, but for this kind of issue I recommend to use the "issues" section because, likely, you get the solution faster. Ok,...

> I agree that we will need a parameter container to manage these parameters, but I am not sure about the first option "yaml and creating std::function" because I have...

> Yes, exactly. You can find the explanations in Gabriel's presentations from analysis meetings, R3B collaboration meetings and also from our last R3B workshop. Ok, I see. But do you...

Very nice. I also intended to open an issue about what we have discussed in the meeting. But now you have done that for me. Thanks. But let me first...

> Hm... a week perhaps? Minimally a week is fine. But should we have different time requirements for different types of PR? Some PRs are just bug fixes, which only...

> Seriously, I don't think there is a good way to codify each eventuality. I think it is fine to say "the maintainers will decide what happens", which is what...