# Mojo 1.0 Beta **URL:** https://forum.modular.com/c/mojo/mojo-1-0-beta/32.md [Latest](https://forum.modular.com/latest.md) · [Categories](https://forum.modular.com/categories.md) · [Tags](https://forum.modular.com/tags.md) --- ## [About the Mojo 1.0 Beta category](https://forum.modular.com/t/about-the-mojo-1-0-beta-category/3036)
**Author:** [@Modular](https://forum.modular.com/u/Modular)\ **Replies:** 0\ **Last updated:** [May 7, 2026, 4:15pm UTC](https://forum.modular.com/t/about-the-mojo-1-0-beta-category/3036 "2026-05-07T16:15:22Z")
Mojo 1.0 is in beta and we’re actively listening! Post your questions, feedback, and early impressions here. For bugs and feature requests, head to GitHub Issues and use the Mojo 1.0 label. --- ## [Mojo Pro now supports Mojo 1.0.0b2](https://forum.modular.com/t/mojo-pro-now-supports-mojo-1-0-0b2/3359)
**Author:** [@Bodiam](https://forum.modular.com/u/Bodiam)\ **Replies:** 3\ **Last updated:** [August 31, 2026, 10:12am UTC](https://forum.modular.com/t/mojo-pro-now-supports-mojo-1-0-0b2/3359 "2026-08-31T10:12:36Z")
Hi all, I’m the author of Mojo Pro (https://plugins.jetbrains.com/plugin/31943-mojo-pro), a plugin for the Jetbrains products I’m maintaining. For those who are interested, I’ve just updated the plugin with the new Mojo … --- ## [Writing Float64 into numpy via UnsafePointer corrupts when also reading another float64 buffer (Mojo 1.0b3)](https://forum.modular.com/t/writing-float64-into-numpy-via-unsafepointer-corrupts-when-also-reading-another-float64-buffer-mojo-1-0b3/3371)
**Author:** [@Curious](https://forum.modular.com/u/Curious)\ **Replies:** 3\ **Last updated:** [August 7, 2026, 1:00am UTC](https://forum.modular.com/t/writing-float64-into-numpy-via-unsafepointer-corrupts-when-also-reading-another-float64-buffer-mojo-1-0b3/3371 "2026-08-07T01:00:35Z")
We build a Python extension with PythonModuleBuilder and need a fast path that fills preallocated numpy float64/int64 buffers from Mojo (COO weight build). Pattern that fails on \`Mojo 1.0.0b3.dev2026080406\` + numpy 2.5… --- ## [Provide an option to require explicit \`var\` declarations](https://forum.modular.com/t/provide-an-option-to-require-explicit-var-declarations/3207)
**Author:** [@christoph\_schlumpf](https://forum.modular.com/u/christoph_schlumpf)\ **Replies:** 24\ **Last updated:** [July 31, 2026, 4:16pm UTC](https://forum.modular.com/t/provide-an-option-to-require-explicit-var-declarations/3207 "2026-07-31T16:16:02Z")
Mojo has two variable declaration styles: “explicit block scoped var declarations” and “implicit function scoped variable declarations” Both styles can be mixed, even inside one function. This can lead to confusion an… --- ## [Where did parallelize go :)?](https://forum.modular.com/t/where-did-parallelize-go/3357)
**Author:** [@Curious](https://forum.modular.com/u/Curious)\ **Replies:** 5\ **Last updated:** [July 31, 2026, 12:48pm UTC](https://forum.modular.com/t/where-did-parallelize-go/3357 "2026-07-31T12:48:51Z")
In Mojo 1.0.0b3.dev2026072906 (8235c7f9) We do not have parallelize hein? I guess I assumed once it was in 1.0.b2\` it would stay there. Seems like Mr. Lattner and the people at Modular are working on Concurrency Support … --- ## [Accelerator-side code and stability](https://forum.modular.com/t/accelerator-side-code-and-stability/3099)
**Author:** [@owenhilyard](https://forum.modular.com/u/owenhilyard)\ **Replies:** 1\ **Last updated:** [May 22, 2026, 1:18am UTC](https://forum.modular.com/t/accelerator-side-code-and-stability/3099 "2026-05-22T01:18:03Z")
As we approach 1.0, I think it needs to be determined what stdlib code is supported on accelerators and what is not, or at least a framework created for discussing this for a particular stdlib feature. For instance, Lis… --- ## [DevicePassable closures: a requirement for HPC programmers](https://forum.modular.com/t/devicepassable-closures-a-requirement-for-hpc-programmers/3046)
**Author:** [@bwibking](https://forum.modular.com/u/bwibking)\ **Replies:** 6\ **Last updated:** [May 9, 2026, 2:55pm UTC](https://forum.modular.com/t/devicepassable-closures-a-requirement-for-hpc-programmers/3046 "2026-05-09T14:55:30Z")
I’ve created a feature request here for making closures DevicePassable: \[Feature Request\] Make closures DevicePassable · Issue #6507 · modular/modular · GitHub. I think this feature is going to be a requirement for HPC … --- ## [FYI - \_\_moveinit\_\_ and \_\_copyinit\_\_ are now hard errors](https://forum.modular.com/t/fyi-moveinit-and-copyinit-are-now-hard-errors/3045)
**Author:** [@quantumwaffles](https://forum.modular.com/u/quantumwaffles)\ **Replies:** 0\ **Last updated:** [May 8, 2026, 4:47pm UTC](https://forum.modular.com/t/fyi-moveinit-and-copyinit-are-now-hard-errors/3045 "2026-05-08T16:47:38Z")
\_\_moveinit\_\_ and \_\_copyinit\_\_ are hard errors in 1.0 beta, they’re no longer silently rewritten. they used to be auto-rewritten to the unified \_\_init\_\_(\*, take:) / \_\_init\_\_(\*, copy:) But in 26.3, your code now fails to…