Native-comp in Emacs 27: Should I keep it enabled for use-package?

Goal

To establish a repeatable development environment that leverages Emacs 27’s native‑comp feature for faster startup and execution.

Constraints

Native‑comp is enabled by default but can trigger crashes in packages that use eval or dynamic byte‑code generation. No comprehensive compatibility list exists, so it is unclear which third‑party packages will behave correctly.

Unresolved Decision

Whether to leave native‑comp globally enabled, disable it for specific packages, or rely on a fallback to bytecode when a crash occurs.

Questions

• Does enabling native‑comp in Emacs 27 reliably support use-package without causing startup failures?
• What documented workarounds exist for packages that fail under native‑comp?
• Should developers disable native‑comp globally or selectively to maintain stability?