A Flatpak may have to ship with an independent copy of a lot of basic developer tools, and even then I don't know whether I want two different versions of git access the same local repository with a chance of incompatible repository formats.
FWIW I was recently able to get a "passable" but not ideal Rust/LSP/Rust-Analyzer/Cargo setup mostly functional via use of the kate build plugin and e.g `flatpak-spawn --host cargo build`...
...and... `flatpak-spawn --host cargo run | sed --unbuffered 's/\x1b\[[0-9;]*m//g'`.
Excuse the cough. :D (It was necessary to remove the ANSI colour codes produced by some logging library the project used.)
(My preference would be to use AppImage but unfortunately recent Kate AppImage versions have a hang-on exit bug.)
https://docs.flatpak.org/en/latest/introduction.html#reasons...
> Flathub only hosts stable application releases, and not development snapshots.
from https://github.com/flathub/flathub/wiki/App-Submission
> If there’s an app that you'd like to be distributed on Flathub, the best first course of action is to approach the app’s developers and ask them to submit it. Remember that for some projects or communities, this may be the first that they have heard of the Flatpak technology or interacted with somebody who advocates it.
Also from the above link.