Redesign loggers
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.8k
- Forks
- 388
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 15
Description
Summary:
From @bob-carpenter
Our loggers should just take these, as in:
logger.info() << "Gradient evaluation took " << ...;
Or we should have a polyadic info function that could look like:logger.info("Gradient evaluation took ", deltaT, " seconds");
Description:
Our loggers were introduced as a stepping stone to getting us to a better design.
We can use this issue to discuss different designs for the loggers.
Additional Information:
cc @sakrejda
Original comment from: https://github.com/stan-dev/stan/pull/2570#r201154784
Current Version:
v2.17.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Begin by reviewing the current logger design and the linked discussion, then compare the proposed streaming and polyadic APIs; done requires an agreed design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100