heh, not really. "ndk-translation" is a really annoying name, but unfortunately we don't get to choose other team's project names :-(
i've sent a link to that bug to the ndk-translation and flutter teams because -- even if the ndk-translation folks fix their bugs [there look to be multiple unrelated bugs on that one github issue] -- the flutter folks will probably want to avoid generating the problematic code patterns until/unless everyone's running the latest ndk-translation with all the fixes.
but, no, nothing for the ndk here :-)