What is Bun's philosophy as it relates to feature parity with Jest? Would Bun create features that are currently not supported by Jest?

[dwjohnston]

Bun's approach for the test runner appears to be a sensible one - create a test framework with an (almost) identical API as Jest, this allows for an easy migration.

What I'm wondering is there are a some features that are requested of Jest, that have not been implemented, for example:

• Make test name available in beforeEach() and afterEach() jestjs/jest#7774
• [Feature]: Predicate matching on snapshot values jestjs/jest#15081

Is it worth requesting these features of Bun? Or does Bun explicitly have the policy of 'we aren't going to implement anything that Jest is not already doing?'.