Mac Malone

This is not currently supported. It is on the TODO list though.

@lecopivo Yes, I certainly hope to have v4.1 out by the end of the month.

Unfortunately, due to currently heavily parallel nature of Lake builds, this is not very feasible at the moment. There is currently no way, within Lake itself, to know what the...

A wrinkle in @Kha's solution is that Lake starts all tasks immediately linking them together (via `Task.bind`) based on dependencies. So there are no tasks are spawned regardless after the...

This is actually as intended as part of @gebner's #52. Note this statement from the PR: "In this fallback mode, all files except lakefile.lean immediately fail with an error to...

@Kha I agree that the message can be confusing. However, as @gebner was responsible for this behavior (and seems to have specifically intended it), I want to hear his input...

> For the latter part, should we store the lakefile loading error in `LAKE_INVALID_CONFIG` so that we can show it instead of this generic message? What error are we talking...

@gebner > Passing (the last couple lines of) the error message should be easily possible. Yeah, this seems reasonable. The only problem right now is that logs are currently printed...

I thought about this some more and have a question: How do you propose setting the environment Lake uses? Are you envisioning having to pass a flag e.g., `-Edev` to...

@Julian I am a little confused as to how that would apply here. I imagine the goal here is not to run a shell (as this issue, at least as...