Tom Kaitchuck
Tom Kaitchuck
Right now everything is hard coded to /_ah/pipeline/ This is an odd string, it would be better if it were configurable.
Because the UI attempts to load all the information needed to display the outline in a single http request, and AppEngine caps data returned to 32MB if the info required...
Right now the threshold for using a Fanout task to write tasks to the task queue is 0. This makes no sense. See AppEngineBackEnd.transactionallySaveAll()
Currently pipeline triggers a taskqueue request many more times than it really needs. E.g. creating a child job with N immediate values and 1 future value will trigger N taskqueue...
Currently there is no way to fail an asynchronous job. The promise has to be filled with a value that indicates a failure. This is not ideal.
Often collections are used in loops where multiple updates/operations are performed at once. If there were a way to perform multiple updates at once these could be made more efficient....
It would be good to incorporate a guide for sealed traits such as https://predr.ag/blog/definitive-guide-to-sealed-traits-in-rust/
As mentioned here https://www.reddit.com/r/rust/comments/1efgisu/trait_definitions_to_avoid_orphan_rule/ It is possible to allow users to avoid the orphan rule when applied to one of your traits by adding an unused associated type.
It would be good to add an entry explaining magic functions. Such as https://lunatic.solutions/blog/magic-handler-functions-in-rust/