~bfiedler

Trackers

~bfiedler/typing-is-hard

Last active 22 days ago

~bfiedler/go-threema

Last active 6 months ago

#9 Add language Ada/SPARK 22 days ago

new content added by ~bfiedler on ~bfiedler/typing-is-hard

#9 Add language Ada/SPARK 22 days ago

Comment by ~bfiedler on ~bfiedler/typing-is-hard

That's a good idea, do you have some references I could use? I can try to look for something myself, but currently my studies take up a lot of my time, which means I will update this as soon as I find the time and motivation.

#13 Add definition for System F 22 days ago

Comment by ~bfiedler on ~bfiedler/typing-is-hard

Thanks for the issue. I've added a short explanations which should give some intuition what System F is and why it is useful, as well as a link to the wikipedia page and references to the undecidability (or not) of type inference. Let me know if I could add anything else!

REPORTED RESOLVED FIXED

#12 Decidability of Idris type-checking 22 days ago

Comment by ~bfiedler on ~bfiedler/typing-is-hard

Thanks for your thoughts. I've detailed the reason why I find it surprising (namely naïve implementations of dependent types have undeciable type-checking).

REPORTED RESOLVED FIXED

#11 Undecidability of Haskell type-checking 22 days ago

Comment by ~bfiedler on ~bfiedler/typing-is-hard

Thanks for the clarification. I've removed mentions to System F, as the other links are already provide sufficient reasons.

REPORTED RESOLVED FIXED

#10 Undecidability of OCaml type-checking 22 days ago

Comment by ~bfiedler on ~bfiedler/typing-is-hard

Thanks, I've updated the description to mention the undecidable problem, and not an implementation issue

REPORTED RESOLVED FIXED

#1 Expose SetGatewayURL 6 months ago

on ~bfiedler/go-threema

REPORTED RESOLVED FIXED

#1 Expose SetGatewayURL 6 months ago

Ticket created by ~bfiedler on ~bfiedler/go-threema

This would make testing and running behind proxies easier.

#10 One statusline per tab 9 months ago

Comment by ~bfiedler on ~sircmpwn/aerc2

Makes sense. I'm playing around with prefixing the account name for that problem - both solutions would be fine with me. (Maybe even have both - a short popup telling you "problem in account xyz" and a persistent tab notification until you switch to the account?)

It's an interesting question how this plays with the composition or the msgview widget, since they are their own widget but have an associated account - I'm not sure how to handle this right now but I will play around a bit more and report back on the feel.

#10 One statusline per tab 9 months ago

Comment by ~bfiedler on ~sircmpwn/aerc2

I've modified my fork to have one statusline per account, and it works fine. There's still some debate left about the following: Should errors be pushed to the host tab also? I think they are important enough to the user to be visible even when focusing on a different account. Then we could PushStatus them to the host tab to make the user aware of them and use SetError on the account tab for a more permanent view.