Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P purr-data
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 363
    • Issues 363
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 54
    • Merge requests 54
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Jonathan Wilkes
  • purr-data
  • Merge requests
  • !383

Closed
Created Jun 19, 2020 by Jonathan Wilkes@jwilkesOwner
  • Report abuse
Report abuse

WIP: port vanilla symbol method for [float], first draft of easing atom ambiguity

  • Overview 1
  • Commits 2
  • Pipelines 2
  • Changes 3

Will be adding workarounds for various atom type ambiguities as possible.

Need to address:

  • [symbol 123(
  • 123 when it's a symbol atom selector

My current approach is to adds "hints" to the error messages when a class has no method to handle an incoming message.

For [symbol 123( we probably want to print out an initial error so that it doesn't slip through silently.

There are probably other cases to do with [route] and friends who have the correct methods but handle matching in surprising ways for new users. We may be able to print warnings in that case.

Edited Jun 20, 2020 by Jonathan Wilkes
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: improve-type-oddities