Skip to content

Conversation

@Manishearth
Copy link
Contributor

This also moves a lot of internal stuff to taking TimeZone instead of &TimeZone. I think that's fine but I can revert if requested.

@Manishearth Manishearth requested a review from nekevss September 13, 2025 23:44
@Manishearth
Copy link
Contributor Author

This is a draft because I want to test it in V8 first, but it's reviewable

@Manishearth Manishearth marked this pull request as ready for review September 14, 2025 00:47
@Manishearth
Copy link
Contributor Author

v8 side: https://chromium-review.googlesource.com/c/v8/v8/+/6946460

cc @linusg this may be annoying to migrate over, but should buy a teensy bit of performance

@Manishearth
Copy link
Contributor Author

Also there is a slight chance Diplomat's choice of type to represent usize isn't perfect. It ought to be fine, but so far Temporal hasn't had usizes over FFI and now it will.

@linusg
Copy link
Contributor

linusg commented Sep 14, 2025

Fine by me 👍

@Manishearth Manishearth merged commit e28b788 into boa-dev:main Sep 14, 2025
8 checks passed
@Manishearth Manishearth deleted the tz-ffi-copy branch September 14, 2025 17:09
hubot pushed a commit to v8/v8 that referenced this pull request Sep 15, 2025
Split this out into a second PR for easier reviewability.

boa-dev/temporal#572 makes TimeZone no longer
need an allocation, which is a bit more invasive change than most.

This was done in preparation for temporal_rs 0.1.0, and we expect far
fewer C++ API breaking changes after that version.

Bug: 401065166
Change-Id: I6a6a6964dfdea50a54902530276bb52060cebf84
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6946460
Auto-Submit: Manish Goregaokar <manishearth@google.com>
Commit-Queue: Leszek Swirski <leszeks@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Cr-Commit-Position: refs/heads/main@{#102467}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants