- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 567 for yield4x (0.19 sec)
-
test/range4.go
package main var gj int func yield4x(yield func() bool) { _ = yield() && yield() && yield() && yield() } func yield4(yield func(int) bool) { _ = yield(1) && yield(2) && yield(3) && yield(4) } func yield3(yield func(int) bool) { _ = yield(1) && yield(2) && yield(3) } func yield2(yield func(int) bool) { _ = yield(1) && yield(2) } func testfunc0() { j := 0
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Mon Jan 08 16:00:53 UTC 2024 - 5.1K bytes - Viewed (0) -
docs/en/docs/tutorial/dependencies/dependencies-with-yield.md
## A database dependency with `yield` For example, you could use this to create a database session and close it after finishing. Only the code prior to and including the `yield` statement is executed before creating a response: ```Python hl_lines="2-4" {!../../../docs_src/dependencies/tutorial007.py!} ``` The yielded value is what is injected into *path operations* and other dependencies:
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Sat Feb 24 23:06:37 UTC 2024 - 14.1K bytes - Viewed (0) -
docs/de/docs/tutorial/dependencies/dependencies-with-yield.md
# Abhängigkeiten mit yield FastAPI unterstützt Abhängigkeiten, die nach Abschluss einige <abbr title="Manchmal auch genannt „Exit Code“, „Cleanup Code“, „Teardown Code“, „Closing Code“, „Kontext Manager Exit Code“, usw.">zusätzliche Schritte ausführen</abbr>. Verwenden Sie dazu `yield` statt `return` und schreiben Sie die zusätzlichen Schritte / den zusätzlichen Code danach. !!! tip "Tipp" Stellen Sie sicher, dass Sie `yield` nur einmal pro Abhängigkeit verwenden.
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Sat Mar 30 18:10:29 UTC 2024 - 13.5K bytes - Viewed (0) -
docs/ru/docs/tutorial/dependencies/dependencies-with-yield.md
**FastAPI** использует их "под капотом" с этой целью. ## Зависимости с `yield` и `HTTPException` Вы видели, что можно использовать зависимости с `yield` совместно с блоком `try`, отлавливающие исключения. Таким же образом вы можете поднять исключение `HTTPException` или что-то подобное в завершающем коде, после `yield`.
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Tue Apr 02 04:21:06 UTC 2024 - 19.6K bytes - Viewed (0) -
docs/em/docs/tutorial/dependencies/dependencies-with-yield.md
⚫️ 5️⃣📆 😋 🤚 `HTTPException` ⚖️ 🎏 🚪 📟, ⏮️ `yield`. ✋️ **⚫️ 🏆 🚫 👷**. 🚪 📟 🔗 ⏮️ `yield` 🛠️ *⏮️* 📨 📨, [⚠ 🐕🦺](../handling-errors.md#_4){.internal-link target=_blank} 🔜 ✔️ ⏪ 🏃. 📤 🕳 😽 ⚠ 🚮 👆 🔗 🚪 📟 (⏮️ `yield`). , 🚥 👆 🤚 `HTTPException` ⏮️ `yield`, 🔢 (⚖️ 🙆 🛃) ⚠ 🐕🦺 👈 ✊ `HTTPException`Ⓜ & 📨 🇺🇸🔍 4️⃣0️⃣0️⃣ 📨 🏆 🚫 📤 ✊ 👈 ⚠ 🚫🔜. 👉 ⚫️❔ ✔ 🕳 ⚒ 🔗 (✅ 💽 🎉), 🖼, ⚙️ 🖥 📋.
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 8.6K bytes - Viewed (0) -
docs/zh/docs/tutorial/dependencies/dependencies-with-yield.md
在 `yield` 后抛出 `HTTPException` 或类似的异常是很诱人的,但是**这不起作用**。 带有`yield`的依赖中的退出代码在响应发送之后执行,因此[异常处理程序](../handling-errors.md#install-custom-exception-handlers){.internal-link target=_blank}已经运行过。没有任何东西可以捕获退出代码(在`yield`之后)中的依赖抛出的异常。 所以,如果在`yield`之后抛出`HTTPException`,默认(或任何自定义)异常处理程序捕获`HTTPException`并返回HTTP 400响应的机制将不再能够捕获该异常。 这就是允许在依赖中设置的任何东西(例如数据库会话(DB session))可以被后台任务使用的原因。 后台任务在响应发送之后运行。因此,无法触发`HTTPException`,因为甚至没有办法更改*已发送*的响应。
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 10.3K bytes - Viewed (0) -
docs/ja/docs/tutorial/dependencies/dependencies-with-yield.md
**FastAPI** はこれを実現するために内部的に使用しています。 ## `yield`と`HTTPException`を持つ依存関係 `yield`と例外をキャッチする`try`ブロックを持つことができる依存関係を使用することができることがわかりました。 `yield`の後の終了コードで`HTTPException`などを発生させたくなるかもしれません。しかし**それはうまくいきません** `yield`を持つ依存関係の終了コードは[例外ハンドラ](../handling-errors.md#_4){.internal-link target=_blank}の*後に*実行されます。依存関係によって投げられた例外を終了コード(`yield`の後)でキャッチするものはなにもありません。
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 12.5K bytes - Viewed (0) -
tensorflow/compiler/mlir/tensorflow/transforms/breakup-islands.cc
OpBuilder builder(&island.GetBody(), island.GetBody().begin()); tf_executor::YieldOp yield = island.GetYield(); if (yield.getNumOperands() == 0) { builder.create<TF::NoOp>(island.getLoc(), TypeRange{}, ValueRange{}); } else if (yield.getNumOperands() == 1) { Value operand = yield.getOperand(0); auto identity = builder.create<TF::IdentityOp>(island.getLoc(),
Registered: Sun Jun 16 05:45:23 UTC 2024 - Last Modified: Fri Aug 11 20:52:36 UTC 2023 - 16.7K bytes - Viewed (0) -
src/runtime/sema_test.go
func testSemaHandoff() bool { var sema, res uint32 done := make(chan struct{}) // We're testing that the current goroutine is able to yield its time slice // to another goroutine. Stop the current goroutine from migrating to // another CPU where it can win the race (and appear to have not yielded) by // keeping the CPUs slightly busy. var wg sync.WaitGroup for i := 0; i < GOMAXPROCS(-1); i++ { wg.Add(1) go func() {
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Jun 21 19:37:22 UTC 2022 - 4.2K bytes - Viewed (0) -
tensorflow/compiler/mlir/tensorflow/transforms/parallel_execute_to_islands.cc
Block& execute_block = parallel_execute_op.GetRegionBlockWithIndex(i); // Replace terminator with tf_executor.YieldOp. Operation* terminator = execute_block.getTerminator(); builder->setInsertionPoint(terminator); auto yield = builder->create<tf_executor::YieldOp>( terminator->getLoc(), terminator->getOperands()); terminator->erase(); // Create new island for each region.
Registered: Sun Jun 16 05:45:23 UTC 2024 - Last Modified: Thu Jan 19 19:47:16 UTC 2023 - 11.1K bytes - Viewed (0)