Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix inputHack in SSP/IMods #467

Closed
JacquesCarette opened this issue Feb 26, 2018 · 2 comments
Closed

fix inputHack in SSP/IMods #467

JacquesCarette opened this issue Feb 26, 2018 · 2 comments
Labels
needs-action-items A clear 'path to resolution' is needed to close any ticket.

Comments

@JacquesCarette
Copy link
Owner

Better than the hack that was there before... but it's still a hack.
@JacquesCarette JacquesCarette mentioned this issue May 11, 2020
Closed
2 tasks
@balacij balacij added the needs-action-items A clear 'path to resolution' is needed to close any ticket. label Apr 26, 2023
@balacij
Copy link
Collaborator

balacij commented Jul 18, 2024

I'm not quite sure what our closing criteria is. However, we don't appear to have inputHack anywhere in our codebase and considering we don't generate code for SSP, I think that whatever this issue was about will come up again when we bring SSP to up to speed and generate code for it. As such, I think we can close this ticket for now.

@balacij balacij closed this as not planned Won't fix, can't repro, duplicate, stale Jul 18, 2024
@smiths
Copy link
Collaborator

smiths commented Jul 18, 2024

I agree with closing this issue. Once we have vectors, hopefully we can get SSP to generate code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-action-items A clear 'path to resolution' is needed to close any ticket.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@smiths @balacij @JacquesCarette