Make -Ylog:X log only phase X

[smarter]

There is no need to log the phase after X anymore, containsPhase does
the correct thing.

Review by @odersky

[odersky]

That was not the reason for the code. The reason was that most of the time the transformer of a phase runs in the next phase. Compensating that in the logging command is tricky - we'd need to know what is the next phase, which is not always clear.

[smarter]

OK, do you think it'd be useful to have an option to explicitly log only the specified phase? Currently -Ylog:frontend generates a lot of output because of how often firstTransform is run.

[odersky]

Yes, I think this calls for a more nuanced command line syntax.

-Ylog:phaseX+

for logging at phase after phaseX, maybe?

• Martin

On Sat, Dec 13, 2014 at 6:09 PM, Guillaume Martres <[email protected]

wrote:

OK, do you think it'd be useful to have an option to explicitly log only
the specified phase? Currently -Ylog:frontend generates a lot of output
because of how often firstTransform is run.

—
Reply to this email directly or view it on GitHub
#273 (comment).

Martin Odersky
EPFL

[smarter]

This could be generalized to -Ylog:phaseX+N to log N phases after phase X, would that be useful?

[odersky]

What would be a use case for this? If there's no convincing one, I would
say let's keep it simple.

• Martin

On Sat, Dec 13, 2014 at 8:01 PM, Guillaume Martres <[email protected]

wrote:

This could be generalized to -Ylog:phaseX+N to log N phases after phase
X, would that be useful?

—
Reply to this email directly or view it on GitHub
#273 (comment).

Martin Odersky
EPFL

[smarter]

I don't see one, so I'll try to implement your original proposal.

[odersky]

OK, thanks!

On Sat, Dec 13, 2014 at 9:24 PM, Guillaume Martres <[email protected]

wrote:

I don't see one, so I'll try to implement your original proposal.

—
Reply to this email directly or view it on GitHub
#273 (comment).

Martin Odersky
EPFL

[smarter]

Superseded by #308 .