sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Update 'flutter screenshot' to fail better if a device doesn't support screenshots
Labels: c: new feature,tool,a: quality,customer: dream (g3),P2,team-tool,triaged-tool

I'm using Flutter master branch version 1a374d820de32d359c06a8ecf0e1348e3ce69a5a, and the following error happened although the `flutter device` does show a connected Moto G4 device:

```
liyuqian@liyuqian:~/Downloads$ flutter devices
3 connected devices:

Moto G 4 • ZY2245H6KS • android-arm    • Android 7.0 (API 24)
Linux    • Linux      • linux-x64      • Linux
Chrome   • chrome     • web-javascript • Google Chrome 75.0.3770.100 

liyuqian@liyuqian:~/Downloads$ flutter screenshot
No supported devices connected.
Must have a connected device
liyuqian@liyuqian:~/Downloads$ flutter screenshot --type=skia --observatory-uri=http://127.0.0.1:35603/atA841bQWXA=/
No supported devices connected.
Must have a connected device
```

The app that I ran is
```
liyuqian@liyuqian:~/flutter/flutter/dev/benchmarks/macrobenchmarks$ flutter run --profile
Initializing gradle...                                              0.7s
Resolving dependencies...                                           1.3s
Launching lib/main.dart on Moto G 4 in profile mode...
Running Gradle task 'assembleProfile'...                                
Running Gradle task 'assembleProfile'... Done                       1.2s
Built build/app/outputs/apk/profile/app-profile.apk (8.0MB).

An Observatory debugger and profiler on Moto G 4 is available at http://127.0.0.1:35603/atA841bQWXA=/
For a more detailed help message, press "h". To quit, press "q".

```

This blocks fixing a P0 bug for a Google's internal client.
Repository: youtube-dl
Issue: Blogger Video Support
Labels: site-support-request

## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.07.02. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.07.02**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs
- Single video: https://www.blogger.com/video.g?token=AD6v5dz18g_1SzBsAhKc1WrVQTXonlsRYUGqRv3GQ0pRq8zd9j0UTjOofODFRLRzVYrVEkne0gq1XtesVPk37EsSG7AX9qlpHwVvbfnVTTao6gdWnq_EUA-lz2QYAESDovwV0ZdXPeP5

## Description
Link was embedded within a Blogger Blog

WRITE DESCRIPTION HERE
Add support for the extraction - it's YouTube/YouTube-like style (uses some youtube embed) so I believe it should be supported and also not too hard to do so probably
Repository: TypeScript
Issue: [Feature request] sort literals in .d.ts
Labels: Suggestion,Effort: Difficult,Experience Enhancement

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section.

-->

## Search Terms

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

## Suggestion

<!-- A summary of what you'd like to see added or changed -->

sort string literal in .d.ts

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

avoid string literal random change order when source code didn't change
and make code history is more easy read

in this issue thread `string literal` is mean => `"a" | "c" | "b"`

this not only happen on `Record`, it has chance happen at all type is auto create by typescript emit with `string literal`

## Examples

<!-- Show how this would be used and what the behavior would be -->

> `"a" | "c" | "b"` is create by typesctipt emit and some time will random change order

- https://github.com/bluelovers/cjk-convert/blob/1a0ba9f85e0bf7fe916158cc14a4ef87507106d9/lib/zh/table/table.ts#L1619-L1635
- https://github.com/microsoft/TypeScript/issues/30328
  - https://github.com/bluelovers/novel-travis-test/commit/3b88745e187736797d9a30d4f4bbd927b0c6dd30#diff-3006c96d8657ccca5b9b3618a256314c
  - https://github.com/bluelovers/novel-travis-test/commit/d33c4a61602a8536d1414d36e027eb99845104f1#diff-3006c96d8657ccca5b9b3618a256314c
  - https://github.com/bluelovers/novel-travis-test/commit/2d749195c39ef386e6c4bad1ae6e19d007c03e93#diff-3006c96d8657ccca5b9b3618a256314c

### current .d.ts output

---

```ts
export declare const table_plus: Record<"a" | "c" | "b">
// "a" | "c" | "b" is random change order
```

### in this request

> sort ( use simple array.sort() ) it when output emit at `.d.ts`

```ts
export declare const table_plus: Record<"a" | "b" | "c">
```

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [ ] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [ ] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).

*Maintainer's note* [@sandersn]: To implementers: When you implement this, be sure to sort other literal types too. Consider sorting other things, like symbol, by the order of their string representation.
Repository: rust
Issue: Coherence violation when inherent method is added to type
Labels: A-trait-system,T-compiler,T-types

It seems that because inherent methods are always called before trait methods, when a dependency adds an inherent method to a struct (which _should_ be a backwards-compatible change to its API requiring no major semver bump) your code that was previously calling a trait method on that struct will (silently) switch to calling the inherent method.

As an example, I could make an extension trait for `Option` defining a method named `foo`, publish `my_cool_crate`, and then if an inherent method named `foo` is added to `Option` in a new version of `core` then my crate can suddenly behave differently despite merely upgrading my Rust compiler. Perhaps it could also fail to compile (like if the signature is "compatible" at the callsite but then a typechecking error happens elsewhere).

I'm not sure if this is a coherence violation or not, or whether this has already been observed/discussed elsewhere. (Had no luck when I searched for github issues about it.)
Repository: rust
Issue: `size_of_val` in a generator can make the generator bigger
Labels: C-enhancement,T-compiler,A-coroutines,I-heavy,C-optimization

Consider the following code:

```rust
async fn foo() {
  let mut x = get_future();
  dbg!(std::mem::size_of_val(&x));
  x.await
}
```

Today, having the `dbg!` line _roughly doubles_ the size of the future returned by `foo`. More precisely, it causes us to allocate storage for `x` twice (once for `x`, and once for the `pinned` variable that `x` is moved into inside the `await`).

This unfortunate state of events is caused by the fact that we cannot "peer into" `size_of_val` and see that the address of `x` never escapes the function. Without knowing this, we can't optimize away the storage of `x` once it has been moved.

This was first discussed here: https://github.com/rust-lang/rust/issues/59123#issuecomment-501401232. One promising solution ([suggested](https://github.com/rust-lang/rust/issues/59123#issuecomment-501472425) by @RalfJung) is that we inline all occurrences of `size_of_val` (and possibly some other intrinsics) in a MIR pass, before we get to the generator transform.
Repository: flutter
Issue: Review plugins lifecycle
Labels: engine,a: existing-apps,P2,a: plugins,team-engine,triaged-engine

go/flutter-plugin-registration

Review the plugin framework for add-to-app scenarios where either 

- plugins might never be invoked or needed during the application's runtime but nevertheless can run code or latch onto host application events
- multiple flutter engines are created but not all engine instances need all plugins
Repository: vscode
Issue: [json] format on save should remove last trailing comma in JSON with json-language-features
Labels: feature-request,json

I am using `json-language-features` to autoformat my JSON/C files but sometimes I accidentally add a last trailing comma on some props or forget one while moving props around. `json-language-features` will print an error then but does not autoformat it and removes the last comma or adds a missing which IMO would be very helpful.

Previously I used prettier (`json-stringify`-parser) which removed missing commas and formatted it well, but I wanted to use build in extensions to do most of the things.

Input:

```json
{
  "nyc": {
    "extension": [
      ".ts",
      ".ts"
      ".ts",
    ]
  }
}
```

Expected:

```json
{
  "nyc": {
    "extension": [
      ".ts",
      ".ts",
      ".ts"
    ]
  }
}
```

Reality:

```json
{
  "nyc": {
    "extension": [
      ".ts",
      ".ts" <-- Expected comma
      ".ts", <-- Trailing comma
    ]
  }
}
```
Repository: terminal
Issue: Epic: Add configuration options for font rendering things (fallback, line height, ligatures, ...)
Labels: Issue-Feature,Area-Rendering,Product-Terminal



```[tasklist]
### Tasks
- [x] #759
- [ ] #2664
- [x] #1298
- [ ] #5093
- [ ] #3498
- [ ] #956
- [x] #1751
- [x] #5828
- [x] #6049
- [ ] #10231
```


### consider (backlog)

- [x] #6678 should we support fractional point sizes?

#### original content

This is a summary from #714 #455
- To properly handle box drawing characters we may need ability to explicitly set line height **in pixels** (to avoid rounding error). We may also need baseline position settings to avoid clipping.
- For the arrow issue, we may need the ability to support specifying a fallback sequence of fonts rather than a master font, pretty like how CSS works.
   - We may also need some method to allow WT to change how it measure characters in a fallen font?
- Option for antialiasing modes — at least for the case that the console's background _isn’t_ transparent.
Repository: pytorch
Issue: "Floating point exception" after trying the method from the issue #22382
Labels: oncall: jit,triaged

in order to use libtorch c++ API.I tried an example from:https://pytorch.org/tutorials/advanced/cpp_export.html#a-minimal-c-application.
Firstly, I got the same bug report with issue #22382.
Then, I tried the method from it and 'make' succeed!
Howerver, I got the problem 'Floating point exception' after executing './example model.pt'
I debug and find the problem was caused by the code 'at::Tensor output = module.forward(inputs).toTensor()'
and I don't know why?

cc @suo
Repository: terminal
Issue: Feature request: create new profile from .lnk file
Labels: Issue-Feature,Help Wanted,Area-Settings,Product-Terminal

# Summary of the new feature/enhancement

Development environments, such as Visual Studio, SDKs, etc. install shortcuts that open command prompts with a pre-configured environment (e.g. "x64 Native Tools Command Prompt for VS 2019"). It's tedious and error prone to copy settings from these shortcuts. Terminal should do it automatically, either on a shortcut-by-shortcut basis, or even better letting you dynamically import a whole directory of shortcuts

# Proposed technical implementation details

Until Terminal has a UI for creating and editing profiles, this feature will simply involve changes to the schema of profiles.json

I propose a new key for profile dictionaries, let's call it "`importDefaultsFromLnk`", which can specify a path to a shell link (.lnk) file. A profile can contain a single `importDefaultsFromLnk` field and nothing else, and all settings will come from the shell link and its `NT_CONSOLE_PROPS` and `NT_FE_CONSOLE_PROPS` data blocks (except those that don't make sense for Terminal, of course, like `NT_CONSOLE_PROPS::dwWindowOrigin`); the `name` field would default to the file's display name (`IShellItem::GetDisplayName`), so that it would automatically hide the extension and/or load a localized description that might be present. If other profile fields are explicitly specified, they'll override settings from the shell link. A `null` value for a field could be used to mean "override with the Terminal default"

Importing a set of shortcuts from a directory (e.g. all shortcuts in Programs folder "Visual Studio 2019\Visual Studio Tools\VC", or even better all shortcuts under "Visual Studio 2019\Visual Studio Tools", recursively) could be done naively, with a profile field that we might call "`importProfilesFromDirectory`", but unlike importing a single shortcut this feature has non-trivial implications, including but not limited to:
- should profiles imported from a directory be grouped in a sub-menu of the "new tab" menu?
- what about recursively imported profiles? should there be sub-sub-menus?
- how do we specify a dynamically imported profile in `globals\defaultProfile`?
Repository: go
Issue: x/mobile: iOS project won't compile with framework built by gomobile
Labels: help wanted,NeedsInvestigation,mobile

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.6 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/myname/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/myname/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/opt/go/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/opt/go/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/cy/b0lrq2m55js29jlf_hhm4xtc0000gn/T/go-build880588199=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I created a go package and used gomobile to bind it for iOS:

```
gomobile bind -v  -target=ios mypackage
```

And then referenced the framework in my iOS project

Then complied the iOS project

### What did you expect to see?

The project should compile

### What did you see instead?

error messge

ld: in /PATH_TO_THE_FRAMEWORK(go.o), building for iOS, but linking in object file (/PATH_TO_THE_FRAMEWORK(go.o)) built for , for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Repository: TypeScript
Issue: Dead return statements in a generator should offer a did-you-mean-yield codefix
Labels: Suggestion,Experience Enhancement

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 -->
<!--
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the CONTRIBUTING guidelines: https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ
-->

<!-- If you have a QUESTION:
   THIS IS NOT A FORUM FOR QUESTIONS.
   Ask questions at http://stackoverflow.com/questions/tagged/typescript
    or https://gitter.im/Microsoft/TypeScript
-->

<!-- If you have a SUGGESTION:
  Most suggestion reports are duplicates, please search extra hard before logging a new suggestion.
  See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md
-->

<!-- If you have a BUG:
  Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.0.0-dev.201xxxxx

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**  yield return generator

Currently it is possible to have the following code:
**Code**

```ts
async function *myGeneratorFunction(): AsyncIterableIterator<number> {
    return 1;
    return 2;
    return 3;
}
```

**Expected behavior:**
A generator function that yields numbers 1 - 3

**Actual behavior:**
No syntax/runtime error but due to a human mistake the generator function is useless.

I copy/pasted an existing generator function, deleted the body with the new implementation and mistakenly used `return` instead of `yield`.

It would be nice if TypeScript could warn when it's encountering a `return` with an actual value inside a generator function.
It makes no sense to `return` a value.
Could be combined with a codefix in the IDE: `Did you mean yield?`
**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior --> 

**Related Issues:**
Repository: TypeScript
Issue: Spread with enum index key, invalid members don't trigger errors
Labels: Needs Investigation

**TypeScript Version:**  3.5.1

**Search Terms:**
object spread enum index missing keys 

**Code**
[Playground link has code](https://www.typescriptlang.org/play/#code/KYOwrgtgBAcg9gFwJYDMkGMCGy4gLLAAmSkUA3gFBTVQCCACvQDRU30ASA8jAKIUC+FCqFLxkaLDhAAVAJ4AHYOVbUAYpwAyGzgHUeAERY0oGgJIBpAwKFIQCYACcUmdErGoM2JLnoPgKR1BXACVgdDgHQmVqCCISCAAuWEQPSW98OMgjKAQFYCT3CS9cOUVs0EwAIwAbIiTKuDhazBBrCnCQAGcEKGAADyRu2wBzX39OgpSiqTGAvxAQsIjCAG0AXSgAXigVlWjjGljiSEnxTykCY4gAOgZmPeNcxVPU4pk86-UtXQMmKAeaBUanUoM5qp0lHtBGsANxCAD08Kgpl6fUU6B6CAAFoMcnBQZgkNU-hClJVgNU4AB3dq4bqowbIECjPwoTp4TDyeQjLYMobM2ada5+QhgVwAHj2lAONBWAGtgLIoLZkmc0rhLvE1klpTKDvLFcqQKrXlJSsBtVAGk1gC0AdR+HDjIIAHwACj2btiEDgf3krIAlFsXfsZR16SB+ggkk9gHAUFBvfjtrq9TRrhmk9k09QVv7-Ncjlqdfac4ioBnC8AfXnWVWrms-uWqUhsTkcZ0oOEILE7EQoHAwAg-tjAlAqYPqlFyYnBp0eQrZJ0SfjW1BOljJ1FnETS2nawXY5ayIm41SkvmUNcgbUovwm0iEIhMNVqkrhkgAG48qkOXDDKBPxfMAlFjKAX06fE0EjPc9UwTpCGcBCUCSAAiHFUKgctMEIYhmVRBAHEwUEkApQhO0IOBgE6EAAHIekcP8HF6VssUcWCHRoUtBDTPwEDABxjUjPoECdGh7ylfhwM7FpZAoAM4SAA)

**Expected behavior:**
Missing keys & incorrect value types when I build a nested object using the spread operator with index keys, ought to throw errors for invalid types

**Actual behavior:**
It seems like the child object can have whatever shape I want, the types aren't being checked at all

**Playground Link:** [This is same as above playground link](https://www.typescriptlang.org/play/#code/KYOwrgtgBAcg9gFwJYDMkGMCGy4gLLAAmSkUA3gFBTVQCCACvQDRU30ASA8jAKIUC+FCqFLxkaLDhAAVAJ4AHYOVbUAYpwAyGzgHUeAERY0oGgJIBpAwKFIQCYACcUmdErGoM2JLnoPgKR1BXACVgdDgHQmVqCCISCAAuWEQPSW98OMgjKAQFYCT3CS9cOUVs0EwAIwAbIiTKuDhazBBrCnCQAGcEKGAADyRu2wBzX39OgpSiqTGAvxAQsIjCAG0AXSgAXigVlWjjGljiSEnxTykCY4gAOgZmPeNcxVPU4pk86-UtXQMmKAeaBUanUoM5qp0lHtBGsANxCAD08Kgpl6fUU6B6CAAFoMcnBQZgkNU-hClJVgNU4AB3dq4bqowbIECjPwoTp4TDyeQjLYMobM2ada5+QhgVwAHj2lAONBWAGtgLIoLZkmc0rhLvE1klpTKDvLFcqQKrXlJSsBtVAGk1gC0AdR+HDjIIAHwACj2btiEDgf3krIAlFsXfsZR16SB+ggkk9gHAUFBvfjtrq9TRrhmk9k09QVv7-Ncjlqdfac4ioBnC8AfXnWVWrms-uWqUhsTkcZ0oOEILE7EQoHAwAg-tjAlAqYPqlFyYnBp0eQrZJ0SfjW1BOljJ1FnETS2nawXY5ayIm41SkvmUNcgbUovwm0iEIhMNVqkrhkgAG48qkOXDDKBPxfMAlFjKAX06fE0EjPc9UwTpCGcBCUCSAAiHFUKgctMEIYhmVRBAHEwUEkApQhO0IOBgE6EAAHIekcP8HF6VssUcWCHRoUtBDTPwEDABxjUjPoECdGh7ylfhwM7FpZAoAM4SAA)

**Related Issues:** I'm not really sure what the root limitation that's causing this is so it's hard for me to find similar issues.
Repository: godot
Issue: AnimatedTexture sprite sheet support
Labels: enhancement,confirmed,topic:2d

**Godot version:**
<!-- Specify commit hash if non-official. -->
3.1

**Issue description:**
<!-- What happened, and what was expected. -->
AnimatedTexture is not capable of using AtlasTextures for its frames. When loading an AtlasTexture the animation will stop, and the entire first frame displays.

**Steps to reproduce:**
Create an AnimatedTexture with four frames. Make each frame an AtlasTexture that is one quarter of the Godot Icon.

**Comment:**

We should document which texture types animated texture supports.
I would also like the ability for AnimatedTexture to support sprite sheets, this would make it much easier to configure them in general. And makes it more convenient to use them as shader flipbooks. For effects such as described in this GDC talk: https://www.gdcvault.com/play/1024630/Visual-Effects-Bootcamp-The-Rise (Technically you can do it without sprite sheets. but its quite a hassle because the workflow is dreadfully slow.)
Repository: rust
Issue: Rustdoc should warn about unused reference links
Labels: T-rustdoc,C-enhancement,E-medium,A-intra-doc-links

rustdoc can easily generate external links by using a full URL as the target.  However, this only works with inline links.  It doesn't work when using footnote links, sometimes called "reference links".  If you try to use a full URL as the target of a footnote link, rustdoc will throw up a `intra_doc_link_resolution_failure` warning.  Here's an example.

`src/libs.rs`:
```rust
//!
//! This is an inline link to [`CStr`](https://doc.rust-lang.org/stable/std/ffi/struct.CStr.html).
//! It works!
//!
//! This is an intra-crate footnote link to [`MyType`][MyType].  It also works.
//!
//! This is a footnote link, aka "reference link", to [`OsStr`](OsStr).  It fails :( .
//!
//! [MyType]: t/struct.MyType.html
//! [OsStr]: https://doc.rust-lang.org/stable/std/ffi/struct.OsStr.html
pub mod t {
    pub struct MyType {}
}
```

```
> cargo +nightly doc --no-deps
 Documenting external_reference_link v0.1.0 (/tmp/external_reference_link)
warning: `[OsStr]` cannot be resolved, ignoring it...
 --> src/lib.rs:7:65
  |
7 | //! This is a footnote link, aka "reference link", to [`OsStr`](OsStr).  It fails :( .
  |                                                                 ^^^^^ cannot be resolved, ignoring
  |
  = note: #[warn(intra_doc_link_resolution_failure)] on by default
  = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`

    Finished dev [unoptimized + debuginfo] target(s) in 1.06s
> rustup run nightly rustc --version
rustc 1.36.0-nightly (7d5aa4332 2019-05-16)
```

The workaround is to only use inline links for external targets.  But that uglies up the code, and it requires duplication if the same comment block needs to instantiate the link multiple times.