internal library

What flutter3d_effects builds the liquid's native lanes with, once the hardware layer has placed the work there.

For the engine's placement of the liquid; not covered by semver for applications. Where compute runs is the hardware layer's to say: FrameCompute.placeHosted answers whether the lanes run the work, and placeKernelLiquid builds them from that answer. A library of its own rather than a src/ import so the dependency is one the API snapshot sees; the structure rule "where compute runs is the hardware layer's to say" names any other file that imports it.

Functions

kernelLiquidOnLanes({SimulationProfile profile = SimulationProfile.deterministic, FluidSolver rest = const DartFluid()}) → KernelLiquid?

The liquid with its pair loops on the native lanes, for a run under profile; null where they are refused — a bit-exact profile, whose bytes must be the CPU kernel's on every machine — or not there: the browser, a build with no C compiler.