fzz 4mo ago • 100%
f16 and f128
Great!👍🏻 What about FPU and VFP support?
fzz 4mo ago • 100%
Looking to example code in the README I have to say that it is neat! ❤️🔥
But know what? Could be awesome to support char-literals in the parser!
macro. Currently in that example str-literals used as single-char strings.
I mean this for example:
num: num=<"-"? '0'-'9'+ …
Why there dash is str but not a char? Also what about escapes, unicode sequences and binary literals?
fzz 4mo ago • 100%
I suppose there should be something like Crang (“friend” of Shredder) without exoskeleton and covered with spikes, like your Corro.
fzz 4mo ago • 100%
- Мне сложно найти ваше уважение к людям когда вы в как минимум 4 сообщества копипастите один и тот же пост, игнорируя функцию репост, тем самым форся многократно видимость поста, – либо специально, либо по недоразумению, но неприятно;
- Софт пишут люди пока что. Жизнь людей в любой точке планеты пропитана политикой. Следовательно требовать (или молить и надеяться) на то, что софт никак не будет подвержен разностороннему политическому влиянию – как минимум наивно;
- Далее далёкое от претензий на аксиоматичность ИМХО: Страна, проявляющая агрессию к гражданам не только своей, но и другой страны должна караться всеми возможными методами, любыми, дабы остановить или ослабить агрессию.
Sorry for 🇷🇺 lang. Lang is beautiful, but today it’s associated with some madness and shame.
fzz 4mo ago • 100%
I’m not sure is it sarcasm or that’s really not bad short description? 🤔
cross-posted from: https://programming.dev/post/15696807 > That was a hard long adventure, massive refactoring with bug-fixing 🥵
That was a hard long adventure, massive refactoring with bug-fixing 🥵
fzz 5mo ago • 100%
Trying to reduce compilation time, reconfiguring underlying cargo’ build-ctx or just riding off the context and using only build-plan and metadata by host cargo & rustc in the cargo-playdate tool.
fzz 5mo ago • 100%
Wowfuck! I've been thinking about an approaching stroke for almost 40 years and it's time to say goodbye. Thank you, that's good news.
fzz 5mo ago • 100%
Nope. This little neat feature mainly is just necessary part of bigger one - const-generics with const bounds.
I really love and regularly use a split keyboard. I’ve been hoping to fix these bugs for many years, for a very long time. The bug has been reported many times by me and other suffering users. No changes in all these years.
Developer — “From start to the latest patch” ; Publisher — “From deal to while the sales are at an acceptable level or the terms of the contract have not yet been fulfilled”; Gamer — “Since I found out about the game and while I come back to it and play”.
fzz 6mo ago • 100%
If I understand you right, I mean just star button on that repo. Thank you 😊
fzz 6mo ago • 83%
I just don’t care, I’m only 40 years old, it’s a kid’s age.
I’m working on a big project in #Rust, there is toolset and API for #Playdate. All going great, moving to stabilization step by step, but I’m tired of looking at the dull 90⭐️. Seriously, could you please throw me into the trends of the github, please! ❤️🔥 [Project repository](https://a.koz.world/playdate), [mastodon](https://gamedev.social/@playdaters).
I’m working on a big project in #Rust, there is toolset and API for #Playdate. All going great, moving to stabilization step by step, _but so tired of looking at the dull amount ⭐️._ [Project repository](https://a.koz.world/playdate), [mastodon](https://gamedev.social/@playdaters).
fzz 7mo ago • 100%
That’s false for closures (or unnamed/inline) functions with context because their type is unique and so you just can’t write their type and that’s not a lang’s fault - that’s logically correct side-effect by-design.
fzz 7mo ago • 100%
Did author knows about difference between static and dynamic dispatch? 🤦🏻♂️
fzz 8mo ago • 66%
Okay, just take a look at code. https://github.com/aeharding/voyager
fzz 8mo ago • 100%
Dada-lang is like dada-art?..
fzz 8mo ago • 100%
Just one question - where it is native? Are you pretty sure?
Just discovered a f*-incredibly useful thing! [Lib.rs Maintainer Dashboard](https://lib.rs/~boozook/dash) is like `brew doctor` but for your crates on crates.io & docs.rs ❤️🔥 It shows outdated deps, docs build errors and a lot of other various things - for all of your crates. I'm thrilled with the find!
Every time when I start using my AirPods, iOS shows me that roll-over. Every single time! How to disable this behavior? Please, any suggestions?
Could be awesome to support app invocation from browser (or any) with url of a post/community/etc.., if host in the url is lemmy instance. In details, there’s two options: 1. Isolated app-only url schema, like “lemmy://lemmy.ml/a/some” 2. Universal, same as implemented in other apps like YouTube, Twitter, GitHub. It should catch urls starting with any-of host of list of lemmy hosts. Second option is better. Actual list of hosts can be determined from https://fedidb.org/ or https://www.fediversesearch.com/ and also, I suppose, can be hardcoded to app/bundle manifest at compile-time.
Trying to configure dosbox-x to properly wrap Gruntz with network support for multiplayer. Any suggestions?
There’s link to the post with spoiler that doesn’t supported by Voyager. It could be great for the app to show a normal spoiler.
I've just create a [little script](https://gist.github.com/boozook/d693415ac0ec0291181241ae733ebc75) to install pip in the latest [Pythonista](http://www.omz-software.com/pythonista) with comfort configuration, as I suppose. This could probably be useful to someone other than me. ::: spoiler screenshots ![IMG_0572](https://github.com/boozook/playdate/assets/888526/f24b5bf1-3cfe-4038-840a-55f9abd88e6e) ![1](https://github.com/boozook/playdate/assets/888526/e7a11bf1-c750-4563-871d-96e632cf335a) ![2](https://github.com/boozook/playdate/assets/888526/deb9c39a-fc1f-4ff5-946b-eeb115269b92) ![3](https://github.com/boozook/playdate/assets/888526/f01a86da-2bf8-4396-b82a-37fbfcadab0a) ___ ::: ❤️🔥
> I just published `futures-concurrency` v7.4.1 which adds support for lending iteration on the newly added `Group` types! > > https://github.com/yoshuawuyts/futures-concurrency/releases/tag/v7.4.1 > > This should replace the final remaining use there was for `select!`, meaning we now have structured alternatives for all kinds of concurrency operations you could possibly want to express.