-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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.
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
MonoVM runtime size-reduction for WebAssembly #43778
Labels
arch-wasm
WebAssembly architecture
area-Meta
size-reduction
Issues impacting final app size primary for size sensitive workloads
tracking
This issue is tracking the completion of other related issues.
Milestone
Comments
Tagging subscribers to this area: @CoffeeFlux |
Dotnet-GitSync-Bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Oct 23, 2020
marek-safar
added
the
tracking
This issue is tracking the completion of other related issues.
label
Oct 24, 2020
marek-safar
changed the title
WASM - Tracking reduction of size on disk investigations
Browser-WebAssembly runtime size reduction tracking
Nov 5, 2020
9 tasks
marek-safar
changed the title
Browser-WebAssembly runtime size reduction tracking
MonoVM runtime size-reduction for WebAssembly
Nov 27, 2020
marek-safar
added
the
size-reduction
Issues impacting final app size primary for size sensitive workloads
label
Dec 9, 2020
9 tasks
a true way to solve this problem is using native-aot for wasm |
@lewing @steveisok - please can one of you take ownership of this. |
github-project-automation
bot
moved this from Needs Consultation
to Done
in Triage POD for Reflection, META, etc.
Dec 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
arch-wasm
WebAssembly architecture
area-Meta
size-reduction
Issues impacting final app size primary for size sensitive workloads
tracking
This issue is tracking the completion of other related issues.
Native code reduction:
.NET 6 Preview 1
.NET 6 Preview 2
.NET 6 Preview 3
.NET 6 Preview 4
Future
The text was updated successfully, but these errors were encountered: