Understanding Stack Trace Availability in Yieldable vs. Custom Errors

I have a question about the utilization of Yieldable errors. Initially, I believed that triggering a Yieldable error like the

BazError

BazError

would provide the stack trace, but it seems that's not the case. However, I've observed that by creating a custom error like

FooError

FooError

, I am able to receive the stack trace. Could you please clarify this ?

  class FooError extends Error {
    readonly _tag = "FooError";
  }

  class FooError extends Error {
    readonly _tag = "FooError";
  }

  class BazError extends Data.TaggedError("Baz")<{
    message: string;
  }> {}

  class BazError extends Data.TaggedError("Baz")<{
    message: string;
  }> {}

I have a question about the utilization of Yieldable errors. Initially, I believed that triggering a Yieldable error like the

BazError

BazError

would provide the stack trace, but it seems that's not the case. However, I've observed that by creating a custom error like

FooError

FooError

, I am able to receive the stack trace. Could you please clarify this ?

  class FooError extends Error {
    readonly _tag = "FooError";
  }

  class FooError extends Error {
    readonly _tag = "FooError";
  }

  class BazError extends Data.TaggedError("Baz")<{
    message: string;
  }> {}

  class BazError extends Data.TaggedError("Baz")<{
    message: string;
  }> {}