Explicitly import ArrayLayouts.MemoryLayout

[nsajko]

Prevent name ambiguity, adapt to changes in nightly Julia, preventing a warning during precompilation.

See:

• Extending a constructor is possible without explicit import or module prefix JuliaLang/julia#25744
• No longer possible to define a function String JuliaLang/julia#57290
• Add a warning for auto-import of types JuliaLang/julia#57311

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.72%. Comparing base (2a479a4) to head (349cb53).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #366   +/-   ##
=======================================
  Coverage   95.72%   95.72%           
=======================================
  Files          17       17           
  Lines        3205     3205           
=======================================
  Hits         3068     3068           
  Misses        137      137           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nsajko]

This is the mentioned warning:

julia> using LazyArrays
Info Given LazyArrays was explicitly requested, output will be shown live 
WARNING: Constructor for type "MemoryLayout" was extended in `LazyArrays` without explicit qualification or import.
  NOTE: Assumed "MemoryLayout" refers to `ArrayLayouts.MemoryLayout`. This behavior is deprecated and may differ in future versions.`
  NOTE: This behavior may have differed in Julia versions prior to 1.12.
  Hint: If you intended to create a new generic function of the same name, use `function MemoryLayout end`.
  Hint: To silence the warning, qualify `MemoryLayout` as `ArrayLayouts.MemoryLayout` or explicitly `import ArrayLayouts: MemoryLayout`
Precompiling LazyArrays finished.
  6 dependencies successfully precompiled in 20 seconds. 3 already precompiled.
  1 dependency had output during precompilation:
┌ LazyArrays
│  [Output was shown above]
└

[dlfivefifty]

I'm completely confused... I thought we already needed to explicitly import MemoryLayout to overload??

But I see we aren't doing this...