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
In #906 the same idea was rejected with the reasoning that const generic was not stablized hence the breakage was not considered as a bug. However, async await in Rust have been stabilized for more than a year now. It is surprizing to see bat still can't highlight it correctly. Can we re-consider the decision?
Thanks.
Quick instructions for anyone searching this in the future:
mkdir -p "$(bat --config-dir)/syntaxes"
cd "$(bat --config-dir)/syntaxes"
git clone https://github.com/rust-lang/rust-enhanced.git
bat cache --build
The text was updated successfully, but these errors were encountered:
In #906 the same idea was rejected with the reasoning that const generic was not stablized hence the breakage was not considered as a bug. However, async await in Rust have been stabilized for more than a year now. It is surprizing to see bat still can't highlight it correctly. Can we re-consider the decision?
Syntax:
async / await in Rust. For example:
Currently it highlights as following:
It should be highlighting
async
andawait
as keywords.Manually installing RustEnhanced can improve the situation:
I understand this is completely up to upstream (https://github.com/sublimehq/Packages), but given the upstream issue sublimehq/Packages#2305 is hinged. I wonder if it makes sense to have bat bundle https://github.com/rust-lang/rust-enhanced/ directly.
In #906 the same idea was rejected with the reasoning that const generic was not stablized hence the breakage was not considered as a bug. However, async await in Rust have been stabilized for more than a year now. It is surprizing to see bat still can't highlight it correctly. Can we re-consider the decision?
Thanks.
Quick instructions for anyone searching this in the future:
The text was updated successfully, but these errors were encountered: