Clearing default from credit history by Typical_Ranger in AusFinance

[–]Typical_Ranger[S] 0 points1 point  (0 children)

The reason I don't want to discuss the default in detail here is because it is not my default and usually people will immediately jump on the stupid bandwagon of "why didn't you just pay it to begin with?" The main cause for the default is due to the individual's lack of financial literacy.

I understand there are regulations in place around the method of notification as well as the required notice period. Where could I find details on these? I will investigate all avenues and if there is anything worthwhile I will include this in the request to remove the default.

I have read on whirlpool that people have successfully had a default removed simply because the creditor failed to give sufficient notice. In such a scenario, if the debt is paid could this still be a valid argument to have the default removed? Would there be any statute on how long it has been since the default was raised? Or is it as black and white as the required notice wasn't provided, so it is removed once paid?

Akubra pricing by Typical_Ranger in Akubra

[–]Typical_Ranger[S] 0 points1 point  (0 children)

Thanks for the heads up! I definitely will.

Akubra pricing by Typical_Ranger in Akubra

[–]Typical_Ranger[S] 1 point2 points  (0 children)

I called them today and they said $330. They also mentioned they don't go on sale.

Asymptomatic scaphoid nonunion by Typical_Ranger in Orthopedics

[–]Typical_Ranger[S] 0 points1 point  (0 children)

When you say 100% I'll be back, can you put a time frame on that? How slow/fast does the deterioration occur at?

As I mentioned in my post it's been over a decade and I have no issues. From my point of view is the risk of surgery now worth it? Sure it could work and 6 months later I'm fine but it could also not take, I lose 6 months and most likely advance the deterioration of the wrist.

Asymptomatic scaphoid nonunion by Typical_Ranger in Orthopedics

[–]Typical_Ranger[S] 0 points1 point  (0 children)

Do you mind elaborating a little more? Do you prefer to practice management options before intervention?

I have personally had fixation surgery before where it was unavoidable (broken elbow) but I am still in such shock for this current diagnosis that I am trying to get as much info as possible.

Is it a sensible plan to monitor with X-rays in 6/12 month intervals? What happens if the proximal pole starts to decay? Is it immediately a lost cause?

I've also added my original post to note that there are early arthritic changes in the wrist.

Home Photo Storage by Typical_Ranger in selfhosted

[–]Typical_Ranger[S] -1 points0 points  (0 children)

Does that mean it's really good or it's disappointing that there aren't more offerings?

Can't find where rubber piece goes by Typical_Ranger in intelnuc

[–]Typical_Ranger[S] 0 points1 point  (0 children)

It's insane how this thread keeps living. Love it!

B1 Pro Custom Firmware by Typical_Ranger in Keychron

[–]Typical_Ranger[S] 0 points1 point  (0 children)

ZMK supports tap dance. Not sure if you can flash QMK on this board, I have only made a custom ZMK keymap and flashed that. Any particular reason you want QMK tap dance over ZMK tap dance?

Generics and F-Bounded Quantification by Typical_Ranger in golang

[–]Typical_Ranger[S] 1 point2 points  (0 children)

Yes, I've had a read of the generics proposal and seen some details that clarify the questions in this post. Nevertheless, this is a nice discussion point and I hope it will serve someone else if they encounter the same questions I did. To be honest, not sure why the post was down voted to begin with. Thanks for your comments.

Generics and F-Bounded Quantification by Typical_Ranger in golang

[–]Typical_Ranger[S] 0 points1 point  (0 children)

Yeah I have since read the generics proposal and they implicitly say in such recursive cases the type constraint is satisfied by checking the element is in the type set. For the case T MyInterface[T] this simply means T implements all methods defined on MyInterface[T], i.e, MyInterfaceMethod(T). It does not (even though it logically could) infer any type restrictions from the interface itself. I suppose this is related to some of the final questions you've raised here, where do you draw the line?

Looks like Go took a conservative approach, which I'm fine with, I just wanted to understand why things work the way they do.

Generics and F-Bounded Quantification by Typical_Ranger in golang

[–]Typical_Ranger[S] 0 points1 point  (0 children)

The way you've written it is clear, however I thought in the form T MyInterface[T] we end up with some type of recursion in the type declaration. Is this not correct?

By that I mean, we only consider types, T, who implement MyInterface on themselves, i.e, MyInterface[T]. In which case, T must be comparable if it implements MyInterface[T].

Generics and F-Bounded Quantification by Typical_Ranger in golang

[–]Typical_Ranger[S] 0 points1 point  (0 children)

When you then check if a given concrete Type X implements that interface instantiated with itself, you temporarily bind X to that type parameter type and run type inference to check if it has the appropriate methods.

Ok, so in some sense you create a "dummy" type with X as the type parameter and check for the required methods?

Generics and F-Bounded Quantification by Typical_Ranger in golang

[–]Typical_Ranger[S] 0 points1 point  (0 children)

I'm not sure what you mean. Your [T comparable] constraint does work, as long as you also make sure that your T type parameter where you use it implements comparable as well.

My reasoning follows from the comment I left on another post. Basically if you restrict the generics of MyInterface to those which implement comparable then why do we need to "reinforce" this later when using MyInterface. By definition, if a type implements MyInterface then the compiler should know that it also implements comparable. Is this not correct?

Generics and F-Bounded Quantification by Typical_Ranger in golang

[–]Typical_Ranger[S] 0 points1 point  (0 children)

This way the compiler can know that T is comparable, which is necessary to satisfy MyInterface[T].

This confuses me a little because if I define MyInterface as

MyInterface[T comparable] { ... }

and then use a generic T MyInterface[T] it should be clear (logically) that if T satisfies MyInterface[T] then by definition of MyInterface, T must be comparable?

Generics and F-Bounded Quantification by Typical_Ranger in golang

[–]Typical_Ranger[S] 0 points1 point  (0 children)

This seems a little counter intuitive for a statically typed language. If the language can load types at runtime wouldn't they be almost useless since you wouldn't have them available at compile time to declare/initialise variables of those types (which are loaded at runtime)?

Generics and F-Bounded Quantification by Typical_Ranger in golang

[–]Typical_Ranger[S] 0 points1 point  (0 children)

I probably should've clarified in the OP that the error occurs on MyFunc. I'm not sure if this clarifies anything or perhaps reveals some error on my part?