Upgrade Core to e586f557af367c74d08d2818bc4bd0d07c8b20bc

[jviotti]

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[cubic-dev-ai]

No issues found across 19 files

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic</sub>

[augmentcode]

🤖 Augment PR Summary

Summary: Updates the vendored sourcemeta/core dependency to e586f557af367c74d08d2818bc4bd0d07c8b20bc, bringing in new build hardening defaults and migrating Unicode/IDNA table generation away from Python.

Changes:

• Bumps the core revision in DEPENDENCIES.
• Adds additional compiler/linker hardening flags (e.g. MSVC CFG/CET and GCC/Clang stack-clash protection) and refines PIE handling.
• Replaces Python-based IDNA and Unicode UCD code generators with C++ codegen executables driven by custom build commands.
• Introduces reusable helpers in core for line iteration (for_each_line), text splitting/trim/join, and additional numeric parsing (to_uint32_t).
• Refactors UCD/IDNA enums to be generated from macro lists shared with the code generators.
• Fixes an edge-case loop termination in regex set-ops preprocessing.

Technical Notes: The new code generators depend on the updated core text/numeric/io utilities, and the build system now builds and runs those generators as part of producing the generated headers.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

In vendor/core/src/core/idna/CMakeLists.txt:18, sourcemeta_executable(OUTPUT ...) sets SOURCEMETA_CORE_IDNA_CODEGEN_TARGET to the target name (see vendor/core/cmake/common/targets/executable.cmake:27-29), but add_custom_command(COMMAND ...)typically needs the actual executable path (e.g. via$<TARGET_FILE:...>); using the raw target name can make the build fail when the binary isn’t on PATH` (notably with multi-config generators).

Severity: high

Other Locations

• vendor/core/src/core/unicode/CMakeLists.txt:18

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}