Starlight220
Starlight220
I meant API docs. We shouldn't expect users to constantly have frc-docs open in the background.
What of this issue wasn't resolved by #4311?
What's the status of this?
The command epochs use `GetTypeName`, so if that works then why can't it be used here as well? Or does `GetTypeName` not work either?
```cpp #include #include class A { public: virtual ~A() = default; }; class B : public A {}; int main() { A a{}; B b{}; A* ptr{&a}; std::cout
Originally (ie when the command lifecycle was first devised in v1), the thought was that `initialize` would contain only initialization logic; perhaps fill the role of a quasi-constructor that can...
I think that the `unless()` decorator (added in #4244) sufficiently provides an answer for the use case OP mentioned, and we're not looking to confusingly break a core part of...
Does this apply to Java as well?
After discussion, we're changing some details: Instead of using `unique_ptr` directly, which would require *unintuitive* manipulation of `std::move` so we can use decorators (which don't have access to the `unique_ptr`...
Do we want to add unit tests for this functionality? Do we have sufficient tests that ensure it doesn't break existing behavior?