@@ -434,10 +434,11 @@ let print_extra_type_clash_help ~extract_concrete_typedecl ~env loc ppf
434
434
@,\
435
435
@{<info>%s@} is an optional record field, and you're passing an \
436
436
optional value to it.@,\
437
- Optional fields expect you to pass a non-optional value.\n \
437
+ Values passed to an optional record field don't need to be wrapped in \
438
+ an option. You might need to adjust the type of the value supplied.\n \
438
439
\ @,\
439
440
Possible solutions: @,\
440
- - Unwrap the option and pass a concrete value directly @,\
441
+ - Unwrap the option from the value you're passing in @,\
441
442
- If you really do want to pass the optional value, prepend the value \
442
443
with @{<info>?@} to show you want to pass the option, like: \
443
444
@{<info>{%s: ?%s@}}"
@@ -450,10 +451,11 @@ let print_extra_type_clash_help ~extract_concrete_typedecl ~env loc ppf
450
451
" @,\
451
452
@,\
452
453
You're passing an optional value into an optional function argument.@,\
453
- Optional function arguments expect you to pass a non-optional value.\n \
454
+ Values passed to an optional function argument don't need to be wrapped \
455
+ in an option. You might need to adjust the type of the value supplied.\n \
454
456
\ @,\
455
457
Possible solutions: @,\
456
- - Unwrap the option and pass a concrete value directly @,\
458
+ - Unwrap the option from the value you're passing in @,\
457
459
- If you really do want to pass the optional value, prepend the value \
458
460
with @{<info>?@} to show you want to pass the option, like: \
459
461
@{<info>?%s@}"
0 commit comments