[roll] Roll fuchsia [wlan][policy] Use single-threaded constructs

The WLAN Policy service has always used a single-threaded executor, and
we have no foreseeable reason to ever use a multi-threaded executor.
Our types therefore don't need to be "Send + Sync", as they will never
get moved between threads.

We could optionally replace our Arc usage with Rc in a future change.

Inspired by http://fxrev.dev/1045766 and
https://maciej.codes/2022-06-09-local-async.html.

Test: fx test wlancfg-tests
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1149152
Original-Revision: 77dca7efb9fdd7c15d8425b670ebea0c23b09e26
GitOrigin-RevId: 72b74a0bf1507507b15f7e9f9b5ad06112b8402e
Change-Id: Ica7df95ebe1f789d55241983cbe743b43cbb48a2
1 file changed
tree: f5ece54c5f811049d7270b0df110f8a0968d75eb
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.