Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

which lead me to believe I needed to `pool.unwrap().spawn_fn(…)`

```error[E0507]: cannot move out of borrowed content
   --&gt; src/rust/engine/src/graph.rs:115:24
    |
115 |             let pool = context_factory.pool().expect("Uninitialized CpuPool!");
    |                        ^^^^^^^^^^^^^^^^^^^^^^ cannot move out of borrowed content

error: aborting due to previous error
```

guess I need to borrow `self` by value in `Core::pool()` and give the `RwLockReadGuard&lt;Option&lt;CpuPool&gt;&gt;` a lifetime?

<@U054MQUPL> : the first one is because it's an option

so yea, an `unwrap` or `expect("There should be a pool installed")` there

<@U054MQUPL> : ah... so `unwrap`/`expect` "takes" the value

you want a reference to the thing instead, which looks like:

`fn as_ref(&amp;self) -&gt; Option&lt;&amp;T&gt;`

editted the `unwrap` above... it doesn't take by reference, and that's the issue

so `as_ref()` gives you a new option containing a reference, which you can consume

btw, was also thinking that engaging the folks on /r/rust - and welcoming contribs.. might help net us some opensrc contribs from rust saavy folks

and might give us a street cred advantage w/ the rust community (re: their roadmap to integrate better with build systems) if part of the build system is written in it

open source headcount == no bounds :slightly_smiling_face:

hmm, no luck with the `pre_fork()` approach