It depends on the way you look at it. Conda manages an environment where it pulls down pre-defined bundles that need to have been prepared to work with each other, and it then allows you to use and share those environments. It doesn’t allow an environment to depend on each other, though.
That’s exactly what we have with snaps. Conda’s packages are snapcraft parts, and Conda’s environments are snaps. There’s a rich language and ecosystem around snapcraft parts already, and they can be bundled together to form a usable environment inside the snap. You then share the snap, which is the working and blessed environment with pretty rich semantics.
We even have some ways to have dependencies across snaps already with interfaces. These need to be carefully designed, though, because we want to encourage an ecosystem that works despite people not having to coordinate every single update to avoid breaking each other’s snaps. Other sorts of dependencies will likely be included in the future, but again it needs to be done very carefully to not break that invariant.