jit-diff: handle output better

Open
#105 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
cli, tooling

Research direction

Start at jit-diff's output handling and its calls to jit-dasm. Decide whether reduced default output with a --verbose option or buffering warnings and errors for final display is appropriate; done means warnings and errors are no longer overwhelmed while normal output remains available.

Written by the indexing model from the issue text.

Description

jit-diff outputs quite a lot of text (such as the command lines for every call to jit-dasm). If any warnings or errors are output before or during a run, they can be overwhelmed by the "normal" output. This can be solved in one of several ways:

  1. Display so much less output by default that any warning/error output is easily seen. (All output could be displayed by passing a --verbose switch).
  2. Save all warning/error output, and re-display it at the very end (like the way msbuild does)
Dominant language
C#
Stars
161
Forks
69
Avg merge
1h 56m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/jitutils

All issues in dotnet/jitutils

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.