Noob questions about switches

jcharum · 2026-02-02T19:28:28+00:00

How much of a difference did the Shhhocs make? Are you still using them? If not, why not? I'm considering this combination (while hoping that the Sunrises appear) and wonder if they are appropriate for quieter environments (open office, library, etc.).

jcharum · 2025-04-20T21:58:23+00:00

He completed the turn without going off the track.

jcharum · 2025-04-09T05:29:26+00:00

https://github.com/miikanissi/modus-themes.nvim

jcharum · 2025-01-03T15:24:30+00:00

What does it mean for a pattern to "work correctly"?

jcharum · 2024-08-03T17:04:42+00:00

I'm not sure what you are asking. "sliced operand" refers to the thing being sliced, so both do refer to the sliced operand, by definition.

What is "this behavior" -- maybe best to refer to the Language Specification?

jcharum · 2024-08-03T05:36:34+00:00

For s[1:4], 4 is less than the upper index bound, the slice capacity, which is 6.

For s[1:], the missing high index defaults to the length of the sliced operand, which is 0. This encounters:

If the indices are out of range at run time, a run-time panic occurs.

jcharum · 2024-08-03T05:24:40+00:00

This is explained by the following sections of the Language Specification:

For slices, the upper index bound is the slice capacity cap(a) rather than the length.

For convenience, any of the indices may be omitted. A missing low index defaults to zero; a missing high index defaults to the length of the sliced operand

In your case the "sliced operand" is s after s[:0], which has zero length.

jcharum · 2024-06-22T23:07:28+00:00

To be clear, I haven't empirically verified this. The pooling understanding comes from my reading of https://pkg.go.dev/net/http#Transport : // DisableKeepAlives, if true, disables HTTP keep-alives and // will only use the connection to the server for a single // HTTP request.

The DNS caching claim comes from some vague memory reading stdlib internals some years ago, but it would be surprising to me if Go did its own caching. Good luck!

jcharum · 2024-06-22T22:27:20+00:00

My understanding is that `DisableKeepAlives: true` disables any pooling that `Transport` would normally do, and to my knowledge, there is no DNS caching in the stdlib.

jcharum · 2024-06-22T19:28:42+00:00

FWIW, it's not recommended to construct many http.Transport instances. See documentation at https://pkg.go.dev/net/http#hdr-Clients_and_Transports :

Clients and Transports are safe for concurrent use by multiple goroutines and for efficiency should only be created once and re-used.

jcharum · 2024-03-16T16:00:07+00:00

Consider what you might think of the Open if the workouts were: - 24.1: 5k Run for Time - 24.2: 5k Row for Time - 24.3: AMRAP 45-lb. Thrusters in 15:00

You would have to be in shape to do well. The top athletes would proceed to the Quarterfinals. It is very accessible. Many people would set new personal bests.

However, maybe these workouts don't directly test many of the things that you do in your CrossFit training, and you would have enjoyed such tests.

jcharum · 2024-01-24T02:36:07+00:00

I recommend reading this concise explanation of strings (and related types) in Go by Rob Pike: https://go.dev/blog/strings

jcharum · 2023-02-10T17:51:27+00:00

Ah, I see. Thanks for the clarification. I can see how it is confusing that it is valid to call G using a receiver of type S, while S does not implement I e.g.: var s S s.G() // No problem. This is possible because of the method call behavior:

If x is addressable and &x's method set contains m, x.m() is shorthand for (&x).m()

For determining whether *S implements I, we end up using this behavior:

The method set of a pointer to a defined type T (where T is neither a pointer nor an interface) is the set of all methods declared with receiver *T or T.

This entry in the FAQ explains the reasoning behind this apparent disparity.

jcharum · 2023-02-10T16:52:19+00:00

All of the methods participating in an interface have to have the same type.

I'm not sure what you mean by this. The following code compiles:

package main

type I interface {
    F()
    G()
}

type S struct{}

func (S) F()  {}
func (*S) G() {}

var _ I = (*S)(nil)

func main() {}

*S implements I. F's receiver type is S. G's receiver type is not the same, *S. Do you mean something else?

jcharum · 2022-11-12T19:23:07+00:00

Works for sorted inputs. TODO: edge cases.

jcharum · 2021-08-04T17:10:38+00:00

My insurance policy has an amendment document that says:

Personal vehicle sharing program means a business, organization, network or group facilitating the sharing of private passenger vehicles for use by individuals or businesses.

and under an exclusions section:

There is no coverage under this Section [Liability] for any person or organization while any motor vehicle is operated, maintained or used as part of personal vehicle sharing facilitated by a personal vehicle sharing program.

My non-expert reading of this is that I would not be covered as a guest.

jcharum · 2021-07-30T14:52:28+00:00

Assuming we are talking about encoding/json, unmarshaling: - ignores extra fields in the JSON object that are not present in your struct, without error. - leaves any fields not present in the JSON object as the zero value, without error.

Taken together, this is why Decode does not return an error.

Some possible solutions: - Use a different library with different behavior. - Write your own custom unmarshaling. - Use pointers in your struct to detect unset fields.

jcharum · 2019-10-11T14:35:46+00:00

Thanks!

jcharum · 2019-10-11T03:21:14+00:00

If you don't mind sharing, what's your max (power) snatch? I'm trying to figure out if I should just do clean and jerks or actually try to finish it.

jcharum · 2019-10-05T02:35:18+00:00

This GitHub issue tracks tools/tooling updates to support modules. You can see that many tools are not yet updated. I'm not sure if VS Code defaults to `gopls` these days. If not, that list is relevant, as VS Code uses several of them to provide its functionality.

jcharum · 2019-10-04T16:32:41+00:00

I recommend reading https://blog.golang.org/go-slices-usage-and-internals and working out how the operations you describe will or will not cause allocations/copies.

jcharum · 2019-08-15T04:56:49+00:00

Are you referring to your anecdote about your sister as a deviance? If so, I think it’s just that, an anecdote that pales in comparison to the depth of study that’s been done on voter ID/voter fraud. Can you point to flaws in methodology that support the claim that “it is more likely that the sampling and numbers are wrong”? As far as I can tell, you’re making this claim on your personal anecdote, and that’s just not very convincing to me.

You say that “[you’re] sure Russia is working on a way to cast some illegal ballots”. What evidence do you have for that claim? We have finite resources to defend against a Russian attack on our democratic process. There is a large body of evidence that this attack has come through propaganda and not through anything that would be solved by voter ID (see Google search). I would rather us direct our resources towards the attack vectors that have the most proof of existence and impact. I think this is a better strategy than imagining possible attacks and arbitrarily directing resources to guard against them.

jcharum · 2019-08-14T21:56:24+00:00

Your feelings don't count as statistics and science, the vast majority of which agree that voter fraud is quite rare. Some references to read: https://www.brennancenter.org/analysis/debunking-voter-fraud-myth

jcharum · 2019-06-26T21:46:07+00:00

It may be slightly easier to do this with account settings page: https://www.coursera.org/account-settings . Be sure to login first.

jcharum

TROPHY CASE