Verify canary release

• I verified that the issue exists in Next.js canary release

Provide environment information

Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Home
Binaries:
Node: 16.13.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant packages:
next: 12.1.7-canary.19
react: 18.1.0
react-

Describe the problem

the low level documentation (https://svelte.dev/docs) is not really easy to use ( and incomplete in some cases)
I think if the runtime function contain JSDOC it will help a lot and give the developers an easier way to discover api documentation

additionally it is possible to replace the https://svelte.dev/docs with the generated docs ( with some thing like https://ty

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Summary

Previous issues:

• #25089

💻

• Would you like to work on a fix?

How are you using Babel?

babel-loader (webpack)

Input code

type FuncWithDescription = [
  function: (...args: any[]) => any,
  string: string
]

https://babeljs.io/repl#?browsers=defaults&build=&builtIns=false&corejs=3.6&spec=false&loose=false&code_lz=C4TwDgpgBAYgrgOwMYHUCWwAWARCBnJAJzTGDQHsEoBeKAbQCgooAzRJMygLigAoA

🐛 bug report

When referencing an icon within the shortcuts attribute of a manifest file. The icon does not resolved like other icons in the same file.

This works:

"icons": [
        {
            "src": "./assets/img/icons/shortcut-96x96.png",
            "sizes": "96x96",
            "type": "image/png"
        }
]

however this does not:

"shortcuts" : [
        {

Marked version:
3.x.x

Describe the bug
A clear and concise description of what the bug is.

Right now, import {use} from "markedjs" does not work, this worked in 2.x.x.

To Reproduce
Steps to reproduce the behavior:

Install & import it.
The DefinitelyTyped definitions also mark this incorrectly as being supported still.

A workaround is importing one of the structur

We currently have no lexical support for character literals. While in principle we could reuse string literals for this purpose, it would make code more self-documenting and readable if we had a distinct lexical syntax for character literals versus string literals. Based on the syntactic choices made in other languages, single-quoted text ('x') seems likely to be the best option here. We need a

Describe the feature

Related with swc-project/swc#3859.

We want to establish initial feature parity to existing @swc/cli to plan out migration with possible breaking changes.

These are initial flags we'd like to have.

• config
• config_file
• filename (swc-project/swc#4016)
• env_name
• ignore

Downcasting is not cheap and may produce app termination. Much better to use explicit type narrowing + implicit downcasting like:

class Base {}
class Parent extends Base {}

function foo(base: Base): void {
  if (base instanceof Parent) {
    let parent = base; // implicitly infer as base: Parent
    // use parent
  }
}

instead of

function foo(base: Base): v

I was casually trying out Nim-lang and playing with nimpretty. Ofcourse I decided to mess with a flag called "indent", and nimpretty doesn't seem to handle this.

I don't really have the time to do a full bisect, I just installed it and played around. Felt it was better to report this than to ignore it.

Example run

 ~ :: nim r a.nim
Hint: used config file '/etc/nim/nim.cfg' [Conf]
H

Feature

sys.thread_info

Python Documentation

https://docs.python.org/3/library/sys.html#sys.thread_info

Describe the bug

See example here

When the flag -flto is given to add link-time optimization, it seems that (at least for g++ and clang++; I have not tested others), the output of the assembly changes to something which is not legible.

Steps to reproduce

1. Visit godbolt.org
2. Create some C++ script
3. Add a compiler window.

• When compilin

• I have tried using the latest released version of Numba (most recent is
  visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
• I have included a self contained code sample to reproduce the problem.
  i.e. it's possible to run as 'python bug.py'.

I think I have discovered a very minor bug - or rather inconsistency with numpy - in Numba's implementation