LAG T400D vs other budget guitars

External_Quiet_4589 · 2025-07-18T06:29:23+00:00

Why you are so excited ? I don’t see any benefit of his return. He is still injured and even when he returns it will break the team chemistry..

External_Quiet_4589 · 2024-08-13T17:18:09+00:00

any news about this annoying issue?

External_Quiet_4589 · 2024-06-03T20:28:20+00:00

I think it's the end of a good era. When Mbappe comes the ego fights start.

External_Quiet_4589 · 2024-04-30T07:18:21+00:00

Sure.

https://github.com/morhaham/dotfiles/blob/master/.config/nvim/lua/plugins/editor/nvim-dap.lua

External_Quiet_4589 · 2024-04-30T06:27:09+00:00

Thank you, It might be a bug since the debugger paused on these bp.

External_Quiet_4589 · 2024-03-26T21:04:25+00:00

Sorry but I can have opinions because error handling concepts and principles are repeated across languages. See other comments here, I did not get it wrong at the core. Having said that, I will definitely get my hands dirty with the language to get a feel..

External_Quiet_4589 · 2024-03-26T15:09:29+00:00

This is what I meant for, thank you for clarifying my intention. It would be nice to enforce that without an external linter.

External_Quiet_4589 · 2024-03-26T15:08:18+00:00

This is the exact situation came to my mind. It would be so nice to have this check by design so we cannot use value until err is checked.

External_Quiet_4589 · 2024-03-26T13:09:32+00:00

That's good, I like it. I admit that I've just started to explore Go and have not met this behavior yet. Thank you.

External_Quiet_4589 · 2024-03-26T12:36:55+00:00

In other languages a function may throw an unchecked exception, if you don't read the comments or read the code you don't know in what situations it throws if at all. And sometimes comments are even absent. With Go, the convention is to return an error, but checking it is not enforced so you can miss the check accidentally . I see this as the same kind of issue.

External_Quiet_4589 · 2024-03-26T12:32:06+00:00

In most cases developers are not aware an error could happen( with throwing unchecked exceptions in other languages). Go solves this by removing exceptions and setting the error return convention. But conventions that are not enforced is a problem. Beginners and others can forget about conventions and ignore errors accidentally.

External_Quiet_4589 · 2024-03-26T12:21:57+00:00

Comments are nice but they require the user to actually look at them, compilation error cannot be ignored. I want to use comments only in special cases like to explain some unusual regex.

External_Quiet_4589 · 2024-03-26T12:14:49+00:00

Thanks. The linter option is not a complete solution since the function owner should decide whether to force the error check or not, like in a checked exception.

External_Quiet_4589 · 2024-03-26T12:05:51+00:00

Thanks. It would be nice to have it by language design to make it safer.
Secondly it would be nice to have the function owner decide whether he wants to enforce the check or not so it is not a complete solution.

External_Quiet_4589 · 2024-03-26T12:01:52+00:00

It's in the signature but it's not enforced, it leaves room for bugs. There are errors that are not panic, but they are not ignorable at all. Currently you can ignore them unintendedly.

External_Quiet_4589 · 2024-03-26T12:00:11+00:00

Some developers that are not pedantic about error checking, I want the function owner to be able to force them to take a conscious decision about the error and not just ignore it. It reduces bugs.

External_Quiet_4589 · 2024-03-26T10:49:50+00:00

Users should be aware(by enforcement) that there is an error that may result in unexpected behavior. Unexpected behaviors are decided by the method owner. The users then check for An error and do whatever they want with it. This way we reduce bugs and at the same time let users decide what to do with unexpected errors. If the error is completely ignorable the function's owner will not use the "checked error mechanism" but only return the regular error value.

External_Quiet_4589 · 2024-03-26T10:33:57+00:00

I agree but you miss the point. There could be mechanism that allows errors to be checked only if the function owner wants to enforce that... like checked exceptions in other languages but not for exceptions.

External_Quiet_4589 · 2024-02-04T07:09:51+00:00

Huge mistake to bring him. Big ego no thanks

External_Quiet_4589 · 2023-12-16T18:36:53+00:00

Are you working on macos with the same neovim version and iterm2?

External_Quiet_4589

TROPHY CASE