[
https://issues.apache.org/jira/browse/NLPCRAFT-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270321#comment-17270321
]
Aaron Radzinski commented on NLPCRAFT-111:
------------------------------------------
I think we need to move away from class names for thread pool and have custom
names instead. It's not safe against code refactoring & hard to document. Also,
we somehow need to have a list of all thread pools in the system for
documentation purposes.
> Fix Scala futures global pool usage.
> ------------------------------------
>
> Key: NLPCRAFT-111
> URL: https://issues.apache.org/jira/browse/NLPCRAFT-111
> Project: NLPCraft
> Issue Type: Improvement
> Reporter: Sergey Kamov
> Assignee: Aaron Radzinski
> Priority: Major
> Fix For: 0.7.4
>
>
> Should be refactored. (Do not use import
> scala.concurrent.ExecutionContext.Implicits.global everywhere)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
