You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, a single Parser can only parse in a synchronized format, and the Parser only has one Environment that is used during parsing. On the other hand, all Methods are immutable and would work perfectly fine in an asynchronous environment.
In most cases, JagTag is used just for text processing, and thus async processing is not needed (and would mean more overhead to create additional Environments). However, JagTag is perfectly viable for actions beyond text processing that may take more time (web requests, image manipulation), and forcing creation of a new Parser for each parse is unnecessary.
Allowing asynchronous parsing would mean re-using the Parser but doing one of the following:
Supplying an Environment to be used during parsing
Allowing an empty Environment to be created when parsing begins
Utilizing some sort of 'Action' template that allows 'building' the Environment and then parsing using it
The text was updated successfully, but these errors were encountered:
Right now, a single Parser can only parse in a synchronized format, and the Parser only has one Environment that is used during parsing. On the other hand, all Methods are immutable and would work perfectly fine in an asynchronous environment.
In most cases, JagTag is used just for text processing, and thus async processing is not needed (and would mean more overhead to create additional Environments). However, JagTag is perfectly viable for actions beyond text processing that may take more time (web requests, image manipulation), and forcing creation of a new Parser for each parse is unnecessary.
Allowing asynchronous parsing would mean re-using the Parser but doing one of the following:
The text was updated successfully, but these errors were encountered: