Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Update solution.md#89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
Closed
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
The first two checks turn into two`case`.The third check is split into two cases:
Las primeras dos validaciones se vuelven dos`case`.La tercera validación se separa en dos casos:

```js run
let a = +prompt('a?', '');
Expand All@@ -21,6 +21,6 @@ switch (a) {
}
```

Please note: the `break`at the bottom is not required. But we put it to make the code future-proof.
Nota: El `break`al final no es requerido. Pero lo agregamos para preparar el código para el futuro.

In the future, there is a chance that we'd want to add one more`case`, for example `case 4`.And if we forget to add abreakbefore it, at the end of`case 3`,there will be anerror.So that's a kind of self-insurance.
En el futuro existe una probabilidad de que querramos agregar un`case` adicional, por ejemplo `case 4`.Y si olvidamos agregar unbreakantes, al final de`case 3`,habrá unerror.Por tanto, es una forma de auto-asegurarse.

[8]ページ先頭

©2009-2025 Movatter.jp