Title: Scope graphing does not take into account a language’s standard library · Issue #165 · github/semantic · GitHub
Open Graph Title: Scope graphing does not take into account a language’s standard library · Issue #165 · github/semantic
X Title: Scope graphing does not take into account a language’s standard library · Issue #165 · github/semantic
Description: As reported in #164, people find the lack of standard-library awareness unintuitive and limiting. This is hard, though, as I pointed out in the issue: There are a number of suboptimal solutions: we could re-parse and re-graph the entire ...
Open Graph Description: As reported in #164, people find the lack of standard-library awareness unintuitive and limiting. This is hard, though, as I pointed out in the issue: There are a number of suboptimal solutions: we...
X Description: As reported in #164, people find the lack of standard-library awareness unintuitive and limiting. This is hard, though, as I pointed out in the issue: There are a number of suboptimal solutions: we...
Opengraph URL: https://github.com/github/semantic/issues/165
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Scope graphing does not take into account a language’s standard library","articleBody":"As reported in #164, people find the lack of standard-library awareness unintuitive and limiting. This is hard, though, as I pointed out in the issue:\r\n\r\n> There are a number of suboptimal solutions: we could re-parse and re-graph the entire standard library of a given language before we start graphing user code, which would be prohibitively slow; we could hardcode details of each supported language’s stdlib into Semantic itself, which is bad for maintainability; we could try to do the work in advance and cache it, but getting caching right is really hard. And whatever method we choose needs to scale to all of our core languages and languages not yet integrated with Semantic.\r\n\r\nDo note that just because the scope graphing mechanism is unaware of the standard library doesn’t mean that it ignores stdlib calls—they are tracked and graphed like any other call, they just lack position information. So this isn’t a “we’re missing stdlib support”, it’s a “how do we annotate stdlib calls with their position information (if any), and how do we get that position information from the stdlib?\"","author":{"url":"https://github.com/patrickt","@type":"Person","name":"patrickt"},"datePublished":"2019-06-18T02:46:54Z","url":"https://github.com/github/semantic/issues/165"}
| 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:ca228d61-b45a-d000-1277-9c9273b6614b |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | EB90:38E318:21F27B6:2AEE76D:6B01B106 |
| html-safe-nonce | ab7eb4eb51a784f87db35ce77694c75dd75f502ceaefde74232069eaf4f78ed6 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFQjkwOjM4RTMxODoyMUYyN0I2OjJBRUU3NkQ6NkIwMUIxMDYiLCJ2aXNpdG9yX2lkIjoiNTc5MTg1ODU1MTE1Njc0ODU1MCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 1c3e58e2f8e5fdb197f27ed18f4e50f6e960804f7d32e32e2f24d9fae998f6f8 |
| hovercard-subject-tag | issue:457232980 |
| 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/github/semantic/165/issue_layout |
| twitter:image | https://opengraph.githubassets.com/6797be1fbc92ef272caaac3507a9c1efb9b3cccfb29c283437843374c1296906/github/semantic/issues/165 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/6797be1fbc92ef272caaac3507a9c1efb9b3cccfb29c283437843374c1296906/github/semantic/issues/165 |
| og:image:alt | As reported in #164, people find the lack of standard-library awareness unintuitive and limiting. This is hard, though, as I pointed out in the issue: There are a number of suboptimal solutions: we... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | patrickt |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/github/semantic git https://github.com/github/semantic.git |
| octolytics-dimension-user_id | 9919 |
| octolytics-dimension-user_login | github |
| octolytics-dimension-repository_id | 175839913 |
| octolytics-dimension-repository_nwo | github/semantic |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 175839913 |
| octolytics-dimension-repository_network_root_nwo | github/semantic |
| 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 | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width