Hey everyone, I recently put together a web app that can simultaneously
record your webcam and screen. The backend also uses local LLMs to overlay
your speech with tts. You can find it here:
https://github.com/cheikh2shift/video-recorder
--
You received this message because you are subscribed
On Sat, Sep 20, 2025, 11:41 AM Stephen Illingworth <
stephen.illingwo...@gmail.com> wrote:
> I'm suggesting that there might be a way of implicitly labeling the
> nearest loop. For example:
>
> for {
> switch rand.IntN(3) {
> case 0:
> case 1:
> break for
> case 2:
> }
> }
>
> At the moment, you h
I'm suggesting that there might be a way of implicitly labeling the nearest
loop. For example:
for {
switch rand.IntN(3) {
case 0:
case 1:
break for
case 2:
}
}
At the moment, you have to explicitly define the label:
func main() {
myloop:
for {
switch rand.IntN(3) {
case 0:
case 1:
break myloop
On Sat, 2025-09-20 at 05:11 -0700, Dean Schulze wrote:
> I don't think it was included in the language spec to be a substitute
> for an else in a case statement.
That wasn't the question. You asked if there is a use. That is a use,
and one that allows leftwards code which is conventional in Go.
-
On Sat, Sep 20, 2025, 8:58 AM Stephen Illingworth <
stephen.illingwo...@gmail.com> wrote:
> On Saturday, 20 September 2025 at 16:43:39 UTC+1 Ian Lance Taylor wrote:
>
>
> My recollection is that we discussed how to handle an unlabeled break
> statement in a select statement. Should it break out of
Hi All,
I forgot to mention that there is a new parameter *timing.folder in *config.txt
file, which indicates that it is necessary to reveal the processing time of
each folder, the acceptable values are true and false.
Sorry.
Thank you.
пятница, 29 августа 2025 г. в 21:54:59 UTC+3, alex-code
On Saturday, 20 September 2025 at 16:43:39 UTC+1 Ian Lance Taylor wrote:
My recollection is that we discussed how to handle an unlabeled break
statement in a select statement. Should it break out of the select or
should it break out of the enclosing loop? We wanted break in a switch to
break o
On Sat, Sep 20, 2025, 3:05 AM Dean Schulze wrote:
> The break keyword terminates execution of a select statement, but is there
> any real use for break in a select / case statement?
>
> The select statement executes one of its cases that can proceed or the
> optional default statement and then pr
There is no fallthrough in a select. You can use fallthrough in a switch
case statement to execute the next case but you wouldn't use both
fallthrough and break together.
On Saturday, September 20, 2025 at 6:21:43 AM UTC-6 Matthew Zimmerman wrote:
> It does allow you to avoid a fallthrough at
On Sat, Sep 20, 2025 at 2:11 PM Dean Schulze wrote:
> I was asking about select.
No difference: https://play.golang.com/p/35rcyiWozwn
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from
It does allow you to avoid a fallthrough at the end of the case.
On Sat, Sep 20, 2025, 8:12 AM Dean Schulze wrote:
> I don't think it was included in the language spec to be a substitute for
> an else in a case statement.
>
> On Saturday, September 20, 2025 at 4:49:56 AM UTC-6 Dan Kortschak wrot
I don't think it was included in the language spec to be a substitute for
an else in a case statement.
On Saturday, September 20, 2025 at 4:49:56 AM UTC-6 Dan Kortschak wrote:
> On Sat, 2025-09-20 at 12:24 +0200, Jan Mercl wrote:
> > On Sat, Sep 20, 2025 at 12:05 PM Dean Schulze
> > wrote:
> >
I was asking about select.
On Saturday, September 20, 2025 at 4:26:27 AM UTC-6 Jan Mercl wrote:
> On Sat, Sep 20, 2025 at 12:05 PM Dean Schulze
> wrote:
>
> > The break keyword terminates execution of a select statement, but is
> there any real use for break in a select / case statement?
>
> F
On Sat, 2025-09-20 at 12:24 +0200, Jan Mercl wrote:
> On Sat, Sep 20, 2025 at 12:05 PM Dean Schulze
> wrote:
>
> > The break keyword terminates execution of a select statement, but
> > is there any real use for break in a select / case statement?
>
> For example:
>
> loop:
> for ... {
>
On Sat, Sep 20, 2025 at 12:05 PM Dean Schulze
wrote:
> The break keyword terminates execution of a select statement, but is
there any real use for break in a select / case statement?
For example:
loop:
for ... {
switch ... {
case foo:
The break keyword terminates execution of a select statement, but is there
any real use for break in a select / case statement?
The select statement executes one of its cases that can proceed or the
optional default statement and then program execution continues after the
select {...} block. S
16 matches
Mail list logo
