and that is why it will most certainly block, beca...
# announcements
m
and that is why it will most certainly block, because it asks for
future1.get()
which hasn't been scheduled yet either. Wit just one thread in the underlying pool you have just created a deadlock 😉