Title: Add type hints? · Issue #282 · python/pyperformance · GitHub
Open Graph Title: Add type hints? · Issue #282 · python/pyperformance
X Title: Add type hints? · Issue #282 · python/pyperformance
Description: How would we feel about adding type hints to the pyperformance codebase? Running a type checker on pyperformance might catch some bugs. But more importantly, in my opinion, it would make some parts of the code base a lot easier to read a...
Open Graph Description: How would we feel about adding type hints to the pyperformance codebase? Running a type checker on pyperformance might catch some bugs. But more importantly, in my opinion, it would make some parts...
X Description: How would we feel about adding type hints to the pyperformance codebase? Running a type checker on pyperformance might catch some bugs. But more importantly, in my opinion, it would make some parts...
Opengraph URL: https://github.com/python/pyperformance/issues/282
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add type hints?","articleBody":"How would we feel about adding type hints to the pyperformance codebase?\r\n\r\nRunning a type checker on pyperformance might catch some bugs. But more importantly, in my opinion, it would make some parts of the code base a lot easier to read and reason about -- it would be self-evident what kind of object is being accepted and returned by various functions.\r\n\r\nThere are various tools that we could use to add \"obvious\" type hints quickly to the code base, such as [autotyping](https://github.com/JelleZijlstra/autotyping) and [MonkeyType](https://github.com/Instagram/MonkeyType).","author":{"url":"https://github.com/AlexWaygood","@type":"Person","name":"AlexWaygood"},"datePublished":"2023-04-26T16:34:38.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/282/pyperformance/issues/282"}
| 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:1fe5e55d-5c95-0382-99fe-1398717a5f59 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 8436:21B39C:8B14ED:C16F3C:696A5B88 |
| html-safe-nonce | cb833c8601d9d5ea7879e28b761a9818c4006bc2b409abcbc480811e77a24b14 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4NDM2OjIxQjM5Qzo4QjE0RUQ6QzE2RjNDOjY5NkE1Qjg4IiwidmlzaXRvcl9pZCI6IjEzMzMyNzUwNTU4MDk1MTg0NzMiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | eef36101d14f49a150587a04effd1a3eab626e86cb028d612456436a3f1bd4ed |
| hovercard-subject-tag | issue:1685359183 |
| 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/python/pyperformance/282/issue_layout |
| twitter:image | https://opengraph.githubassets.com/c0d26a41d633d925ea1987242730d0e5fe007d8d284033aa3c5051bf62623750/python/pyperformance/issues/282 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/c0d26a41d633d925ea1987242730d0e5fe007d8d284033aa3c5051bf62623750/python/pyperformance/issues/282 |
| og:image:alt | How would we feel about adding type hints to the pyperformance codebase? Running a type checker on pyperformance might catch some bugs. But more importantly, in my opinion, it would make some parts... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | AlexWaygood |
| hostname | github.com |
| expected-hostname | github.com |
| None | 3f871c8e07f0ae1886fa8dac284166d28b09ad5bada6476fc10b674e489788ef |
| turbo-cache-control | no-preview |
| go-import | github.com/python/pyperformance git https://github.com/python/pyperformance.git |
| octolytics-dimension-user_id | 1525981 |
| octolytics-dimension-user_login | python |
| octolytics-dimension-repository_id | 65949828 |
| octolytics-dimension-repository_nwo | python/pyperformance |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 65949828 |
| octolytics-dimension-repository_network_root_nwo | python/pyperformance |
| 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 | 63c426b30d262aba269ef14c40e3c817b384cd61 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width