Skip to content

New Allocator #621

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
ltan1ms merged 15 commits into from
Apr 8, 2025
Merged

New Allocator #621

ltan1ms merged 15 commits into from
Apr 8, 2025

Conversation

@amrmorsey
Copy link

@amrmorsey amrmorsey commented Feb 19, 2025

  • Does this PR have a descriptive title that could go in our release notes?
  • Does this PR add any new dependencies?
  • Does this PR modify any existing APIs?
    • Is the change to the API backwards compatible?
  • Should this result in any changes to our documentation, either updating existing docs or adding new ones?

Reference Issues/PRs

What does this implement/fix? Briefly explain your changes.

Any other comments?

ltan1ms
ltan1ms reviewed Mar 4, 2025
View reviewed changes
@amrmorsey amrmorsey force-pushed the NewAllocatorsBranch branch 2 times, most recently from 41896db to db147be Compare April 8, 2025 14:51
@amrmorsey amrmorsey marked this pull request as ready for review April 8, 2025 14:53
ltan1ms
ltan1ms reviewed Apr 8, 2025
View reviewed changes
@amrmorsey amrmorsey force-pushed the NewAllocatorsBranch branch from db147be to bed9b72 Compare April 8, 2025 15:10
@ltan1ms ltan1ms merged commit 963918f into microsoft:BANN_save_load_one_file Apr 8, 2025
3 of 33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ltan1ms ltan1ms ltan1ms approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@amrmorsey @ltan1ms