Waffle Maybe

Results 54 issues of Waffle Maybe

It is known that Rust rules about breaking changes are tricky, so it's best we add [cargo-semver-checks](https://github.com/obi1kenobi/cargo-semver-checks) to CI, so that we don't accidentally do a breaking change in a...

K-enhancement
call for contribution
S-blocked
A-meta

_Originally reported in #750._ `Message::filter_reply_to_message()` inserts a `Message` into the dependency map, this message overrides the original message. This makes it impossible to use `Message::filter_reply_to_message()` and retrieve both the original...

FIXME
C-main
A-update-managment

I'm not sure how the implications we chose, the real implications, and `use_independent_chat_permissions` interact. We must figure this out before the release. (this came up during the review of #954)

A-tba-types

For example `ChatMemberUpdated` doesn't. - [ ] Check which kinds don't implement `GetChatId` - [ ] Implement `GetChatId` for them

K-enhancement
call for contribution
C-main
A-tba-types

This \[is needed to\] fix the issue with webhooks not setting allowed updates correctly and thus not getting the updates (lol (lmao)). Sadly, I don't know how to fix the...

S-waiting-on-author
C-main
A-update-listeners

This is one of the interesting bits in tail call implementation — MIR support. This adds a new `TerminatorKind` which represents a tail call: ```rust TailCall { func: Operand>, fn_span:...

T-compiler
S-waiting-on-author
F-explicit_tail_calls

**NB**: this is a breaking change (although arguably a bug fix) and as such shouldn't be taken lightly. This changes `expr?`'s desugaring like so (simplified, see code for more info):...

T-compiler
S-waiting-on-review
T-libs

I'm using `git2` to periodically check changes in a repository. Sometimes I start getting `SSL error: received early EOF; class=Ssl (16); code=Eof (-20)` errors while pulling from the repository (github)....

[`Index`](https://github.com/cavedweller/mikado/blob/f20ee6a4f5ef892e10ff11002de087c13b3af55e/src/memory_region.rs#L22): ```rust assert_eq!(index as usize % mem::size_of::() as usize, 0); ``` [`IndexMut`](https://github.com/cavedweller/mikado/blob/f20ee6a4f5ef892e10ff11002de087c13b3af55e/src/memory_region.rs#L29): ```rust assert_eq!(index % mem::size_of::() as u32, 0); ``` That's a bit strange.

As the title suggests, the only way to stop the bot while it's pulling updates is to `kill` it, which is not ideal.

bug