Title: Suggestion regarding --noCustomAsyncPromise · Issue #7018 · microsoft/TypeScript · GitHub
Open Graph Title: Suggestion regarding --noCustomAsyncPromise · Issue #7018 · microsoft/TypeScript
X Title: Suggestion regarding --noCustomAsyncPromise · Issue #7018 · microsoft/TypeScript
Description: The --noCustomAsyncPromise switch was just introduced #6967. ES7 async functions cannot return custom promises, but their TypeScript counterparts can. This switch makes it so that TypeScript's non-compliant async function behaviour is th...
Open Graph Description: The --noCustomAsyncPromise switch was just introduced #6967. ES7 async functions cannot return custom promises, but their TypeScript counterparts can. This switch makes it so that TypeScript's non-...
X Description: The --noCustomAsyncPromise switch was just introduced #6967. ES7 async functions cannot return custom promises, but their TypeScript counterparts can. This switch makes it so that TypeScript's ...
Opengraph URL: https://github.com/microsoft/TypeScript/issues/7018
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Suggestion regarding --noCustomAsyncPromise","articleBody":"The `--noCustomAsyncPromise` switch was just introduced #6967.\n\nES7 async functions cannot return custom promises, but their TypeScript counterparts can. This switch makes it so that TypeScript's non-compliant async function behaviour is the default, and anyone wanting to maintain ES-compliant code has to provide this switch.\n\nWhy not have an `--allowCustomAsyncPromise` instead? Then anybody can opt in to TypeScript's custom async function behaviour, but is made more aware they are doing something special/non-standard because they need to provide the flag.\n\nThe current polarity of the flag may encourage a great deal more inadvertent use of this non-standard behaviour, causing greater pain down the line when async functions gain better runtime support and adoption. I think it would be prudent to put the non-standard behaviour behind a flag, and make standard behaviour the default.\n","author":{"url":"https://github.com/yortus","@type":"Person","name":"yortus"},"datePublished":"2016-02-11T08:48:13Z","url":"https://github.com/microsoft/TypeScript/issues/7018"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:12d37eec-bafa-21df-d8e5-e271ab256ccb |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | BEC4:683FF:8F2C23:B9E727:6B00DD10 |
| html-safe-nonce | 564270bb87f310a45754f7245a428926202326799c858c1631849ec59302a3a2 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCRUM0OjY4M0ZGOjhGMkMyMzpCOUU3Mjc6NkIwMEREMTAiLCJ2aXNpdG9yX2lkIjoiMjcwMjQ1NTIxMTgzNzkzODk2MCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 289020227941b106dcc1509cf4f87fc623e7ae0eacd9aa7b4bd8467d012d19a6 |
| hovercard-subject-tag | issue:132919222 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/microsoft/TypeScript/7018/issue_layout |
| twitter:image | https://opengraph.githubassets.com/d3e0f92155453526684a5ebff54ad929a77dbfe2119563d8af65688b0b346fda/microsoft/TypeScript/issues/7018 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/d3e0f92155453526684a5ebff54ad929a77dbfe2119563d8af65688b0b346fda/microsoft/TypeScript/issues/7018 |
| og:image:alt | The --noCustomAsyncPromise switch was just introduced #6967. ES7 async functions cannot return custom promises, but their TypeScript counterparts can. This switch makes it so that TypeScript's non-... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | yortus |
| hostname | github.com |
| expected-hostname | github.com |
| None | 043c3f30fbcbe2c6c8e729e10cbbbc90c406546f9fbbb67c648d38f6b7d16daf |
| turbo-cache-control | no-preview |
| go-import | github.com/microsoft/TypeScript git https://github.com/microsoft/TypeScript.git |
| octolytics-dimension-user_id | 6154722 |
| octolytics-dimension-user_login | microsoft |
| octolytics-dimension-repository_id | 20929025 |
| octolytics-dimension-repository_nwo | microsoft/TypeScript |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 20929025 |
| octolytics-dimension-repository_network_root_nwo | microsoft/TypeScript |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 5425dc24e8bd8d6fca9641a12afc984825a43875 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width