Do not pull default engine features into runtime#4879
Conversation
The default features include `temporal` which cannot be deactivated with the previous configuration.
b194c78 to
42bde73
Compare
Test262 conformance changes
Tested main commit: |
|
What is the use case for not wanting to include default features into the runtime? Also, if we are turning it off by default, shouldn't provide corresponding feature flags to turn them back on? |
I want to be able to disable certain engine features like
I've re-enabled the |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4879 +/- ##
==========================================
+ Coverage 47.24% 57.12% +9.87%
==========================================
Files 476 555 +79
Lines 46892 60599 +13707
==========================================
+ Hits 22154 34616 +12462
- Misses 24738 25983 +1245 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I agree with this change. |
|
I'm for this changes as well. Part of the reason why I'm for the same change in the engine too. It's just given me pause because I'm curious if there's a way to ship temporal without any of the data compiled in the binary. But that can be solved by feature flagging the default provider. |
The default features include
temporalwhich cannot be deactivated with the previous configuration.