Tony Allevato

Results 16 issues of Tony Allevato

The new warning about macros lacking a `name` argument conflicts with the established practice that Skylib has been using for Starlark-based tests, which has also been adopted by rules_apple and...

Right now, we only support kind-of-static linking: the `swift_library` targets that the binary depends on are statically linked into the final binary, but the Swift runtime libraries are dynamically linked....

type: feature request
P3

We should provide a way to build a .dylib/.so from Swift code instead of just an executable binary. `cc_binary` does this via the `linkshared` attribute (and requiring a specific name...

type: feature request
P3

Bazel's [platforms](https://docs.bazel.build/versions/master/platforms.html) and [toolchains](https://docs.bazel.build/versions/master/toolchains.html) APIs are the right way going forward to express the toolchains that we create, rather than the ad-hoc mechanism we currently have. Let's migrate to it...

type: cleanup
P3

The repository rule on Linux should detect if the Swift toolchain is not already on the path; if that's the case, and if the user is running one of the...

type: feature request
P2

The ObjcProvider framework migration stuffs everything in the `Modules` directory of a framework into the `modulemap` key, but that's not correct for Swift modules/interfaces. A workaround for this is currently...

type: feature request
P2

The debug console when running our extension shows messages like these at activation time: ``` [UriError]: Scheme is missing: {scheme: "", authority: "", path: "", query: "", fragment: ""} extensionHostProcess.js:76...

type: bug

Many times, BUILD files contain macros that generate targets that are purely implementation details that are meant to be hidden from the user (for example, `ios_application` currently produces a handful...

type: feature request
P2

(From #17) We should leverage Bazel's [Build Event Protocol](https://docs.bazel.build/versions/master/build-event-protocol.html) in the extension so that we can provide various UI feedback about builds the user launches, such as (just some random...

type: feature request

Created my own so we're not stomping on each other's results in the other PR with we both use it.