These methods were added in #857 and were not functionally iterated upon since:

They are affected by several problems:

• It seems to be public API (it's not used anywhere internally), but it's undocumented
• It will cause a deadlock if you remove resources below what an enqueued task requires
• It should trigger _ensure_computing when increasing resources
• It's prone to race conditions, where the scheduler sends a ComputeTaskEvent for a task but the necessary resources are no longer available
• The matching method in Scheduler is ambiguous: it's called add_resources, but its RPC comms handler is called set_resources
• The Scheduler handler should use batched comms, not RPC
• Scheduler.add_resources is also invoked to replace (not add to) the worker resources at every heartbeat - which is unnecessary

CC @mrocklin (who originally wrote #857), @hendrikmakait