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.

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

Provide a way to retag S3Configuration values #75

Closed
ocharles opened this issue Jul 25, 2013 · 3 comments
Closed

Provide a way to retag S3Configuration values #75

ocharles opened this issue Jul 25, 2013 · 3 comments

Comments

@ocharles
Copy link
Contributor

S3Configuration carries a phantom type of the request type. I am storing my S3Configuration in a bigger Env data type, and it's fine if I always do NormalQuerys. However, I need to do both types of queries, so I end up having to do:

    let s3' = case s3 of
                S3.S3Configuration a b c d e f -> S3.S3Configuration a b c d e f

It would be nice if aws provided this inside the library itself.

@aristidb
Copy link
Owner

Can't you use a polymorphic S3Configuration?

@ocharles
Copy link
Contributor Author

My use case at the time was to store the S3Configuration in some other piece of data, so to make it polymorphic meant I would have to introduce a new type parameter for that data type - which I would prefer to avoid. I don't think it's possible to do it with a forall either, because when I create an S3Configuration I am choosing a concrete instantiation of the type parameter.

@aristidb
Copy link
Owner

Hi ocharles,

Tried a newtype wrapper?

Cheers,

Aristid
Am 11.10.2013 17:36 schrieb "Oliver Charles" notifications@github.com:

My use case at the time was to store the S3Configuration in some other
piece of data, so to make it polymorphic meant I would have to introduce a
new type parameter for that data type - which I would prefer to avoid. I
don't think it's possible to do it with a forall either, because when I
create an S3Configuration I am choosing a concrete instantiation of the
type parameter.


Reply to this email directly or view it on GitHubhttps://github.com//issues/75#issuecomment-26146866
.

@aristidb aristidb closed this as completed May 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants