Updating modularml to modular for max and mojo repos now that the Github

org changes

MODULAR_ORIG_COMMIT_REV_ID: b9ef61ba464a2f508359b05dd9a5bea99b2d34c1

CONTRIBUTING.md

@@ -222,7 +222,7 @@ for more details.
 
 #### Fork and clone the repo
 
-Go to the [Mojo repo](https://github.com/modularml/mojo) and click the fork
+Go to the [Mojo repo](https://github.com/modular/mojo) and click the fork
 button:
 
 ![Create Fork](stdlib/docs/images/create-fork.png)

README.md

@@ -26,11 +26,11 @@ This repo includes source code for:
 
 This repo has two primary branches:
 
-- The [`stable`](https://github.com/modularml/mojo/tree/stable) branch, which
+- The [`stable`](https://github.com/modular/mojo/tree/stable) branch, which
 is in sync with the last stable released version of Mojo. Use the examples
 here if you’re using a [release build of Mojo](#latest-released).
 
-- The [`main`](https://github.com/modularml/mojo/tree/main) branch, which
+- The [`main`](https://github.com/modular/mojo/tree/main) branch, which
 is in sync with the Mojo nightly build and subject to breakage. Use this branch
 for [contributions](./CONTRIBUTING.md), or if you're using the latest
 [nightly build of Mojo](#latest-nightly).
@@ -79,7 +79,7 @@ When you clone this repo, you'll be on the `main` branch by default,
 which includes code matching the latest nightly build:
 
 ```bash
-git clone https://github.com/modularml/mojo.git
+git clone https://github.com/modular/mojo.git
 ```
 
 If you want to instead see the source from the most recent stable
@@ -88,13 +88,13 @@ release, then you can switch to the `stable` branch.
 ## Contributing
 
 When you want to report issues or request features, [please create a GitHub
-issue here](https://github.com/modularml/mojo/issues).
+issue here](https://github.com/modular/mojo/issues).
 See [here](./CONTRIBUTING.md) for guidelines on filing good bugs.
 
 We welcome contributions to this repo on the
-[`main`](https://github.com/modularml/mojo/tree/main)
+[`main`](https://github.com/modular/mojo/tree/main)
 branch. If you’d like to contribute to Mojo, please first read our [Contributor
-Guide](https://github.com/modularml/mojo/blob/main/CONTRIBUTING.md).
+Guide](https://github.com/modular/mojo/blob/main/CONTRIBUTING.md).
 
 For more general questions or to chat with other Mojo developers, check out our
 [Discord](https://discord.gg/modular).
@@ -108,6 +108,6 @@ MAX and Mojo usage and distribution are licensed under the
 
 ## Thanks to our contributors
 
-<a href="https://github.com/modularml/mojo/graphs/contributors">
-  <img src="https://contrib.rocks/image?repo=modularml/mojo" />
+<a href="https://github.com/modular/mojo/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=modular/mojo" />
 </a>

examples/check_mod.py

@@ -18,7 +18,7 @@
 FIX = """
 -------------------------------------------------------------------------
 fix following the steps here:
-    https://github.com/modularml/mojo/issues/1085#issuecomment-1771403719
+    https://github.com/modular/mojo/issues/1085#issuecomment-1771403719
 -------------------------------------------------------------------------
 """
 

proposals/byte-as-uint8.md

@@ -40,5 +40,5 @@ and 78 results for `DTypePointer[DType.int8]`.  Replacing
 `DTypePointer[DType.int8]` with `DTypePointer[DType.uint8]` and `Pointer[Int8]`
 with `Pointer[UInt8]` on case by case bases is a substantial refactoring effort,
 but it will prevent a certain class of logical bugs (see
-<https://github.com/modularml/mojo/pull/2098>). As it is a breaking change in
+<https://github.com/modular/mojo/pull/2098>). As it is a breaking change in
 sense of API design, it is sensible to do the refactoring as soon as possible.

proposals/inferred-parameters.md

@@ -49,7 +49,7 @@ scalar_param[DType.int32, Int32()]() # 'dt' parameter is required
 This has been requested multiple times in various forms, especially given the
 new autoparameterization feature. The current tracking feature request:
 
-- <https://github.com/modularml/mojo/issues/1245>
+- <https://github.com/modular/mojo/issues/1245>
 
 ## Proposal
 

proposals/lifetimes-keyword-renaming.md

@@ -2,7 +2,7 @@
 
 Date: October 2024
 
-Previous revision: [[June 2023](https://github.com/modularml/mojo/blob/f8d7cb8ba4c21ec3fbc87e21609b3fd56cab695f/proposals/lifetimes-keyword-renaming.md)]
+Previous revision: [[June 2023](https://github.com/modular/mojo/blob/f8d7cb8ba4c21ec3fbc87e21609b3fd56cab695f/proposals/lifetimes-keyword-renaming.md)]
 
 The design of the Mojo references subsystem is starting to come together.  To
 finalize the major points, it helps to come back and re-evaluate several early

proposals/ref-convention.md

@@ -12,7 +12,7 @@ Mojo’s safe references have evolved and iterated a lot. From the initial
 compiler re-plumbing that made memory-only types possible, to threading
 lifetimes through everything with the introduction of `!lit.ref` to the
 development of a “user-space” Reference type, to the recent discussions about
-[adding automatic dereference to Reference](https://github.com/modularml/mojo/discussions/2594),
+[adding automatic dereference to Reference](https://github.com/modular/mojo/discussions/2594),
 we’ve been iteratively improving the model with a goal of ending up with
 something powerful and explainable.
 
@@ -42,7 +42,7 @@ Along the way, we’ve had a number of challenges to address:
    to `Reference`. It would be awesome to clarify this.
 
 5. We still need to
-   [reconsider which keywords](https://github.com/modularml/mojo/blob/main/proposals/lifetimes-keyword-renaming.md)
+   [reconsider which keywords](https://github.com/modular/mojo/blob/main/proposals/lifetimes-keyword-renaming.md)
    to use for argument conventions. The `inout` keyword, for example, is
    problematic because it works with types that are not movable or copyable. The
    callee doesn’t actually move things in and out, it takes a mutable reference.

proposals/remove-let-decls.md

@@ -1,6 +1,6 @@
 # Simplifying Mojo🔥 - let's get rid of `let`
 
-Chris Lattner, Dec 5, 2023, Status: **Accepted**, [discussion thread](https://github.com/modularml/mojo/discussions/1456#discussioncomment-8358722)
+Chris Lattner, Dec 5, 2023, Status: **Accepted**, [discussion thread](https://github.com/modular/mojo/discussions/1456#discussioncomment-8358722)
 
 Mojo is still a new language, and is rapidly evolving.  We’re learning a lot
 from other languages, but Mojo poses its own set of tradeoffs that indicate a
@@ -10,7 +10,7 @@ One of the early decisions made in Mojo's development is that it adopts the
 `let` and `var` design point that Swift uses.  This whitepaper argues that we
 should switch to a simpler model by jettisoning `let` and just retaining `var`
 (and implicit Python-style variable declarations in `def`).  This has also been
-[suggested by the community](https://github.com/modularml/mojo/issues/1205).
+[suggested by the community](https://github.com/modular/mojo/issues/1205).
 
 Note that immutability and value semantics remain an important part of the Mojo
 design, this is just about removing "named immutable variables".  Immutable
@@ -31,7 +31,7 @@ variables aren't a core programming concept, and not something required
 to achieve Mojo's goals.
 
 2. The naming of `let` caused a lot of early [heat and
-debate](https://github.com/modularml/mojo/discussions/120). Other programming
+debate](https://github.com/modular/mojo/discussions/120). Other programming
 languages have a wide range of design points (e.g. `const` in C/C++ and
 Javascript) and there is a divergence of naming for all these things:
 `let`, `val`, `const`, etc, etc.
@@ -43,7 +43,7 @@ three concepts going around: `alias`, `let`, and `var`.  Most of the uses of
 4. Both Swift and Rust encourage immutable values - Swift (and currently Mojo)
 warn about unneeded mutability, Rust makes mutability more verbose (`let mut`),
 and some propose that Mojo [make mutability more
-verbose](https://github.com/modularml/mojo/issues/451).  This cuts very hard
+verbose](https://github.com/modular/mojo/issues/451).  This cuts very hard
 against a lot of the design center of Python, which doesn’t even have this
 concept at all: it would be weird to make it the default, but if we don’t,
 then why bother having it?
@@ -112,7 +112,7 @@ This would eliminate a bunch of complexity in the compiler as well:
    like: “`let x: Int; x = 1; use(x); x = 2; use(x)`” even though the original
    lifetime of the first “`x=1`” naturally ended and “`x`” is uninitialized
    before being assigned to.  This has always been a design smell, and it
-   [doesn’t work right](https://github.com/modularml/mojo/issues/1414).
+   [doesn’t work right](https://github.com/modular/mojo/issues/1414).
 
 This proposal will not affect runtime performance at all as far as we know.
 

stdlib/README.md

@@ -54,6 +54,6 @@ See the license file in the repository for more details.
 ## Support
 
 For any inquiries, bug reports, or feature requests, please [open an
-issue](https://github.com/modularml/mojo/issues) on the GitHub repository. See
+issue](https://github.com/modular/mojo/issues) on the GitHub repository. See
 the [Mojo contributor guide](../CONTRIBUTING.md) for guidelines on filing good
 bugs.

stdlib/docs/development.md

@@ -107,7 +107,7 @@ You can do the same for a directory with
 All the tests should pass on the `main` branch with the nightly Mojo
 compiler. If you've pulled the latest changes and they're still failing please
 [open a GitHub
-issue](https://github.com/modularml/mojo/issues/new?assignees=&labels=bug%2Cmojo&projects=&template=mojo_bug_report.yaml&title=%5BBUG%5D).
+issue](https://github.com/modular/mojo/issues/new?assignees=&labels=bug%2Cmojo&projects=&template=mojo_bug_report.yaml&title=%5BBUG%5D).
 
 ### Running a subset of the Standard Library Unit Tests
 
@@ -135,7 +135,7 @@ disabled, you can set the environment
 variable `MOJO_ENABLE_ASSERTIONS_IN_TESTS=0`.
 
 If you run into any issues when running the tests,
-[please file an issue](https://github.com/modularml/mojo/issues) and we’ll take
+[please file an issue](https://github.com/modular/mojo/issues) and we’ll take
 a look.
 
 ## Formatting changes

stdlib/src/builtin/simd.mojo

@@ -2247,7 +2247,7 @@ struct SIMD[type: DType, size: Int](
 
     # Not an overload of shuffle because there is ambiguity
     # with fn shuffle[*mask: Int](self, other: Self) -> Self:
-    # TODO: move to the utils directory - see https://github.com/modularml/mojo/issues/3477
+    # TODO: move to the utils directory - see https://github.com/modular/mojo/issues/3477
     @always_inline
     fn _dynamic_shuffle[
         mask_size: Int, //

stdlib/test/builtin/test_issue_1004.mojo

@@ -11,7 +11,7 @@
 # limitations under the License.
 # ===----------------------------------------------------------------------=== #
 # RUN: %mojo %s
-# Test for https://github.com/modularml/mojo/issues/1004
+# Test for https://github.com/modular/mojo/issues/1004
 
 from testing import assert_equal
 

stdlib/test/builtin/test_issue_1505.mojo

@@ -11,7 +11,7 @@
 # limitations under the License.
 # ===----------------------------------------------------------------------=== #
 # RUN: %mojo %s
-# Test for https://github.com/modularml/mojo/issues/1505
+# Test for https://github.com/modular/mojo/issues/1505
 
 from random import random_ui64
 

stdlib/test/builtin/test_simd.mojo

@@ -119,7 +119,7 @@ def test_convert_simd_to_string():
     var c: SIMD[DType.index, 8] = 7
     assert_equal(String(c), "[7, 7, 7, 7, 7, 7, 7, 7]")
 
-    # TODO: uncomment when https://github.com/modularml/mojo/issues/2353 is fixed
+    # TODO: uncomment when https://github.com/modular/mojo/issues/2353 is fixed
     # assert_equal(String(UInt32(-1)), "4294967295")
     assert_equal(String(UInt64(-1)), "18446744073709551615")
 
@@ -129,7 +129,7 @@ def test_convert_simd_to_string():
 
     assert_equal(String(UInt64(16646288086500911323)), "16646288086500911323")
 
-    # https://github.com/modularml/mojo/issues/556
+    # https://github.com/modular/mojo/issues/556
     assert_equal(
         String(
             SIMD[DType.uint64, 4](

stdlib/test/collections/test_list.mojo

@@ -574,7 +574,7 @@ def test_no_extra_copies_with_sugared_set_by_field():
 
 # Ensure correct behavior of __copyinit__
 # as reported in GH issue 27875 internally and
-# https://github.com/modularml/mojo/issues/1493
+# https://github.com/modular/mojo/issues/1493
 def test_list_copy_constructor():
     var vec = List[Int](capacity=1)
     var vec_copy = vec