HomeSort by relevance Sort by last modified time
    Searched refs:encapsulating (Results 1 - 6 of 6) sorted by null

  /prebuilts/go/darwin-x86/src/html/template/
url.go 33 // explicitly indicate that such a URL is expected and safe by encapsulating it
  /prebuilts/go/linux-x86/src/html/template/
url.go 33 // explicitly indicate that such a URL is expected and safe by encapsulating it
  /external/tensorflow/tensorflow/contrib/verbs/
patch_notes_verbs_with_0_copies.md 30 5. With the addition of tensor pre-allocation, we noticed there is a large code similarity between sending the first tensor request and re-sending the request in case of meta-data changes. After implementing a common method for tensor pre-allocation, it turned out that implementation becomes much simpler by encapsulating the process of request sending/re-sending, meta-data response callback and content response callback, all in a single "Request" class. The request class holds all the relevant request information, which reduces excessive parameter passing and lambda capturing. This decision is purely for elegance and code simplicity, and we decided to implement it in first stage because it makes the implementation much easier.
  /prebuilts/go/darwin-x86/src/net/
addrselect.go 173 // If DA is reached via an encapsulating transition mechanism (e.g.,
  /prebuilts/go/linux-x86/src/net/
addrselect.go 173 // If DA is reached via an encapsulating transition mechanism (e.g.,
  /external/libunwind/doc/
libunwind.tex 268 data-structure encapsulating the dynamic unwind info has been designed

Completed in 276 milliseconds