[Bug]: OpenAPI3 fails to consistently emit default float values declared in e-notation.

[ethall]

Describe the bug

OpenAPI3 does not always emit a default float value when declared in e-notation.

When attempting to declare a default float, float32, or float64 less than 0.1, the emitter will drop the default field from the model.

Reproduction

Current behavior from v0.60.0:
Playground Link

Expected behavior from v0.56.0:
Playground Link

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[timotheeguerin]

Weird, also depends on which order you define things. 0.01 defined after 1e-2 will not work but before both work

https://typespec.io/playground?c=bW9kZWwgRU5vdGF0aW9uQmFzaWMgew0KICBjOiBmbG9hdCA9IDFlLTI7xBRkyhQwLjAxOw0KfQ0K&e=%40typespec%2Fopenapi3&options=%7B%7D&version=0.60.x

[ethall]

Sorry to resurrect, but I tested the release containing #4420 and found more test cases where the compiler fails to capture the e-notation values. Should I create a new issue or add to this issue?

[timotheeguerin]

yeah can you open a new issue with all the new cases you found