Title: Should the corresponding error message be added for all asserts? · Issue #1839 · AssemblyScript/assemblyscript · GitHub
Open Graph Title: Should the corresponding error message be added for all asserts? · Issue #1839 · AssemblyScript/assemblyscript
X Title: Should the corresponding error message be added for all asserts? · Issue #1839 · AssemblyScript/assemblyscript
Description: Should the corresponding error message be added for all asserts? I often encountered assert failures before, such as the path of the compilation, but in fact, I have to read the relevant code carefully to know the specific reason, becaus...
Open Graph Description: Should the corresponding error message be added for all asserts? I often encountered assert failures before, such as the path of the compilation, but in fact, I have to read the relevant code caref...
X Description: Should the corresponding error message be added for all asserts? I often encountered assert failures before, such as the path of the compilation, but in fact, I have to read the relevant code caref...
Opengraph URL: https://github.com/AssemblyScript/assemblyscript/issues/1839
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Should the corresponding error message be added for all asserts?","articleBody":"Should the corresponding error message be added for all asserts?\r\nI often encountered assert failures before, such as the path of the compilation, but in fact, I have to read the relevant code carefully to know the specific reason, because there is no related error message for assert.\r\nBefore fixed in https://github.com/AssemblyScript/assemblyscript/pull/1836, some libs will meet errors when `asc ./assembly/index.ts` , but it's ok when `asc ./index.ts`.\r\nThe index.ts is:\r\n```ts\r\nexport * from \"./assembly/index\";\r\n```\r\n\r\nAnd if the developer modifies the AST, the friendly error can let the developer notice the wrong behavior.","author":{"url":"https://github.com/yjhmelody","@type":"Person","name":"yjhmelody"},"datePublished":"2021-04-30T08:03:07Z","url":"https://github.com/AssemblyScript/assemblyscript/issues/1839"}
| 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:273c79b5-4c1f-e2cb-7ead-db9075de9da2 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D26E:17A8A4:60FDA6:8110D5:6B00AA2A |
| html-safe-nonce | b435782d40f8aaaf5ed92e3e3cad69e3ea460b87f3fd30bbd88ed5fa77082858 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEMjZFOjE3QThBNDo2MEZEQTY6ODExMEQ1OjZCMDBBQTJBIiwidmlzaXRvcl9pZCI6IjM5MjU2ODM2ODE4MTI4NTEyNDIiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 52d5333383acf0a1b9eaa5fb362a256ba06c6b61c727094a83c3da77bccc0051 |
| hovercard-subject-tag | issue:872138109 |
| 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/AssemblyScript/assemblyscript/1839/issue_layout |
| twitter:image | https://opengraph.githubassets.com/50a464a135c8d47bfc704c7bc0b97ce2ccd2b16a64cd7f85079f58e3a2116284/AssemblyScript/assemblyscript/issues/1839 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/50a464a135c8d47bfc704c7bc0b97ce2ccd2b16a64cd7f85079f58e3a2116284/AssemblyScript/assemblyscript/issues/1839 |
| og:image:alt | Should the corresponding error message be added for all asserts? I often encountered assert failures before, such as the path of the compilation, but in fact, I have to read the relevant code caref... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | yjhmelody |
| hostname | github.com |
| expected-hostname | github.com |
| None | 455b493e3402a3a3a06beac5d20bb7db3da060808b220aa48d6a7eca7c59863a |
| turbo-cache-control | no-preview |
| go-import | github.com/AssemblyScript/assemblyscript git https://github.com/AssemblyScript/assemblyscript.git |
| octolytics-dimension-user_id | 28916798 |
| octolytics-dimension-user_login | AssemblyScript |
| octolytics-dimension-repository_id | 105138356 |
| octolytics-dimension-repository_nwo | AssemblyScript/assemblyscript |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 105138356 |
| octolytics-dimension-repository_network_root_nwo | AssemblyScript/assemblyscript |
| 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 | 2f575159976167242d488c0b062eb355c4e198b7 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width