Yoshiya Hinosawa

@jsejcksn https://github.com/denoland/deno_std/pull/3874#issuecomment-1864171562 > At one end: a user wants as little configuration and as much "magic" as possible — they expect the offered API to figure out where their ".env"...

Thanks for the fix. One thing I wonder about this solution is that this still prompt the user write permission for the parent dir. I wonder if reverting #3242 can...

@egfx-notifications Thanks for updating, but the introduction of a new option looks too much to me. I'd suggest we would land with the previous version. Could you revert the last...

I came up with another way to solve this issue. If we call `lstat` first, then `mkdir`, then catch only `AlreadyExists`, this solves both race condition and unnecessary write perm...

What is the source of flakiness?

> The semver mod was taken over from node-semver. range actually represents a [range-set](https://github.com/npm/node-semver/blob/main/range.bnf). That BNF file only looks like a non official reference for implementers of node-semver. That doesn't...

I don't think we have such hook in `Deno.test`. These are the current options of Deno.test https://deno.land/[email protected]?s=Deno.TestDefinition

> Is there any possibility to add some similar hook in deno_core, such as before and after? Not sure if we are still open to such addition. When the last...

It might be non ideal, but maybe we can add support of `expect.hasAssertions()` only for `describe` `it` runners. They are wrappers of `Deno.test` and `t.step`, and we can add arbitrary...

> I wonder if it would make sense to rename them to *Includes to align better with the web api and assert mod. The expectation for `std/expect` is the compatibility...